Post #4295507

@cthululemon@social.cthululemon.com to move masto to another server, we do something called a "lift-and-shift" to borrow a term from the construction industry. this is where we shut it down, move all the files, and start it back up. to get in to the extreme details and why's would be to start citing the deep magic that founded the internet, but, the quick and dirty generic process is: -1: take inventory of what exactly is being moved. are you moving volumes and database dumps or only volumes? if so, treat them as separate migrations. do you need to make considerations for networking changes? 0: spend a few hours looking over the configs to see what (if anything) you need to change. config changes are otherwise avoided during migrations. 1: alert your users/temporarily redirect DNS to a maintenance page/otherwise handle obligations you need to for scheduled downtime. 2: stop the stack. 3: do any data dumping that may need to happen. 4: copy & import it to the new host. 5: change the DNS & start the stack. for masto in specific, if you're running the most basic self-contained docker compose stack for it, then you'll really only need to copy the volumes over and won't need to bother with database dumps.