Thanks for that suggestion. Do you know of a good tutorial on this; as I am still getting my head around Docker; or better yet do you mind to describe how to this this here? Before, when I have tried some fancy
Docker tricks I ended up making matters worse.
Yes, this is how I have been doing it so far. Make the major changes in the staging site and then when we are happy with the changes, make a backup,
sftp that backup to the main site and then manually (on the command line), run
discourse restore. This method results in a simple
the site is currently in read only mode (paraphrasing) message and remains up, visible to the users during transition. This works nicely based on my two weeks very noob experience.
However, the two Docker container approach on the same server you mentioned seems interesting as well. The problem, at least for me in my
noobiness, is that when I have tried this in the past (a few times last week), I had major problems getting Discourse to run on ports different than
:443 regardless of how skillful I tried to modify
Basically, I tried:
- cp -rf /var/discourse /var/discourse2
- edit app.yml in /var/discourse2/containers (changing the port mappings for
- ./launcher rebuild app
… and I always get some failure message where Docker cannot access the new ports I have specified like
I’m sure it just a Docker rookie mistake on my part; but I cannot get it to work.
However, this method has worked well for me, consistently:
- Take a backup of production site.
sftp that backup to the staging site
- restore staging site with snapshot from production
- make changes
./launcher rebuild app
- test, and if successful
- make backup of staging site
sftp that backup to the production site
- restore production site with backup from staging site
This is a lot of work to just add our
maxmind key so hopefully I can learn how to get the
two docker container solution to work well.