How to rebuild the site with new server

[zyouchi (ひさし)]

I can not update Discourse to the latest version due to error.

I got an error after updating my forked install

I typed the command as follows cd / var / discourse git pull ./launcher rebuild app I got a caution statement like the following You will less than 5 GB of free space on the disk where / var / lib / docker is located. Filesystem Size Used Avail Use% Mounted on / dev / vda 1 25 G 20 G 4.4 G 82% / (Y / N) y (y / N) y Would you like to try to recover space by cleaning docker images and containers in the system? WARNING! This will remove: - all stopped containers - all networks n…

So I’m thinking about rebuilding the site with a new server.
Please tell me the best way to rebuild the site.

Since I have already published the site and many users are using it, I would like to carefully migrate data etc.

I investigated variously but I am worried about success in my environment.

My environment is as follows.
· I built the site in an official way. (Docker, mailgun, DigitalOcean)
· The plug-in uses only what the official is advancing. (Discourse-adplugin, docker_manager)

[Dax (Daniela)]

See:

Move your Discourse Instance to a Different Server

In this guide we’ll move an existing Discourse instance on Linode (source) to a new Discourse instance on Digital Ocean (destination), but of course these steps will work on any other cloud providers that support Docker. If you are using the same domain name and moving servers, you should set the TTL (time to live) on your DNS entry to a very low value in advance of the change. If you are using different domain names, this won’t matter. Log In and Update Only admins can perform backup…

[bartv (Bart)]

Since you’re on Digital Ocean, you could also consider switching to a larger droplet, or mounting an additional data volume and moving your data there.

[Stephen]

We dealt with the storage issue on this one a few days ago