On Saturday, 4 July, 2020 I plan to move our new site
communitiy.unix.com to a different server.
The new location is currently running fine in a staging configuration and when testing, it appears faster.
The current hosting for
community.unix.com is a 16GB six core VPS slice running Discourse in a docker container on Ubuntu 18.04.
I plan to move this to:
Dedicated hosting with 64 GB RAM and an 8 core Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz.
My server consolidation plans have changed because our dedicated hosting provider has dropped their price of the dedicated server above to the same price as the lower performing VPS it is on now. So, we will have better performance for the same money.
I have already tested Discourse running in a docker container (production mode) on the dedicated server hardware behind an Apache2 reverse proxy and it works great.
Currently, our community discourse app runs behind a
nginx reverse proxy. The additional RAM and CPU power appear to easily compensate for the performance hit of changing the reverse proxy from
apache2. Running the
discourse docker production app behind the
Apache2 reverse proxy permits us to run both the legacy site
community.unix.com on the same dedicated hardware with higher overall performance.
In addition, the new Discourse configuration will run configured with PostgreSQL 12, which I have tested and it is not a problem to restore a new PostgreSQL 12 configuration with a PostgreSQL 10 database dump. This is a more reliable way to upgrade to PostgreSQL 12 in my view (versus trying to upgrade from PG10 to PG12 "on the fly" as many do with mixed results and a lot of downtime) Plus, I have already done this type of upgrade a number of times in test mode, and it works well (without any problems at all).
My plan is to begin to perform this community migration:
Saturday, 4 July 2020, 5:00 AM GMT
At that time, my plan is to:
community.unix.comto read only mode.
- Do a full backup of
- Move that backup to the new server.
- Change the DNS to point to the new server.
community.unix.comon the new server.
- Perform the restore.
The entire process should take around 30 to 45 minutes (let's say 1 hour to be on the safe side).
So, my estimate is:
BEGIN MIGRATION: Saturday, 4 July 2020, 5:00 AM GMT
COMPLETE MIGRATION: Saturday, 4 July 2020, 6:00 AM GMT
If for any reason, the migration fails for any unforeseen reason (I don't think it will, since I have tested this fairly extensively), I will simply change the DNS back to the current site, since the migration does no effect the current configuration.