Discourse InstantApp


#21

The rubygem issue is fixed, libv8 binary is now properly pull.

To update gem on your servers execute the following command:

gem update --system


#22

So what’s now missing to deploy Discourse using Docker? Is there a issue/bugzilla somewhere to follow this afford?


#23

Re-write the Dockerfile for Discourse, the official Dockerfile has x86 dependencies.


#24

I created an issue on github for this: https://github.com/discourse/discourse_docker/issues/121


#25

I used the non-supported guide to update my installation from 1.2.0-beta4 to 1.2.0-beta5. I removed therefore the modifications in Gemfile and Gemfile.lock. DB Migration went flawlessly, but I could not compile the assets because I got a segfault.

So I applied the changes to the Gemfile and stay using the custom provided v8/therubyracer version.
Maybe I missunderstood @edouard when he said that libv8 would not be an issue anymore. Can someone try to reproduce this behavior?


#26

It looks like it is a known issue https://github.com/cowboyd/therubyracer/issues/316 I recommend you to use the custom libv8 at the moment


#27

It might be helpful if you show your interest for arm-support of the official discourse docker image in this issue I created a while ago. So far, nobody commented.

https://github.com/discourse/discourse_docker/issues/121


#28

Postin on meta would get way more attention! Someone should make a post there.


#29

Please do so. :smile: You could link back to this page and to the github issue.


#30

@rriemann There is still issues with libv8 and therubytracer.
We need them to be fixed before working on a Discourse instantapps


#31

Hello, im having problem after running this command (all other till now was fine)


#32

There is an issue with therubyracer, we are waiting for a fix


#33

Hi there,

We just release the Discourse instantapp in beta, you can try it and give us your feedback! :smile:

Here is the documentation https://www.scaleway.com/docs/how-to-use-the-discourse-forum-instant-apps, the image is listed in the ImageHub tab when you create a new server.

Cheers


#34

cc @Moter8 @rriemann @m0k1


#35

That’s good news! You built in based on the existing how-to? Which version is it and how are we supposed to update?


#36

@rriemann version is the latest stable : v1.2.3, let me know if it works fine

The Dockerfile we used to create the image is on github:

I will create a documentation to upgrade the image, but the idea is:

1- Update the Gemfile and Gemfile.lock with the custom libv8 / therubyracer gem, check out the .patch files https://github.com/scaleway/image-app-discourse/tree/master/patches/customgems/patches

2- As discourse use run

bundle install --no-deployment --without test production
sudo su discourse -c "RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate" \
sudo su discourse -c "RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake assets:precompile" \

#37

I’m not using the dockerfile yet. I patched today my version to the most recent version 1.3.0.beta6 and it’s working flawlessly. :smile:

Next, I will try out to patch @edouard’s Dockerfile to use the current beta and the multisite setup.


#38

Great! :smile:
Let me know if you have any issue!

Cheers


#39

These are the last days for testing without caring for (my) money.

I forrked https://github.com/scaleway/image-app-discourse and patched it to the current beta. On your platform I could make a new image and install it to a 2nd volume that I could boot successfully afterwards.

However, this implies many cycles power-off and power-on. I would like to install the image just in place using docker. I’m not an expert in docker. :disappointed: How can I start the container. I tried:

docker run --name discourse -d -p 80:80 armbuild/rriemann-app-discourse

Next question: Your Dockerfile is actually a complete rewrite that is much less flexible. Why didn’t you base your port on the actual https://github.com/discourse/discourse_docker ?

Without a safe path to update discourse, I don’t feel comfortable as there are many security patches and feature updates arriving every week. That’s why the official image allows to rebuild the image based on a predefined receipt.


#40

Hi @edouard, I wonder why v1.2.3 and not the latest stable? is there any reason to use that particular version?