Seems reasonable to me, although I would think you want to shut down the old instance before you do the backup, otherwise you potentially lose any new data between when you take the backup and when you shut down the server.
this post was submitted on 08 Jun 2023
11 points (100.0% liked)
Lemmy
496 readers
2 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
Thats what the "docker-compose down" is for in the second step :)
Derp. Note to self: don't make serious comments after 10pm. My brain skipped right over the word "new" in the line Shutdown on new VPS: docker-compose down.
I'm not familiar with the details of setting up a Lemmy instance, but can't you already get the new instance up and running with a modified /etc/hosts instead of waiting for the DNS to be updated? That might reduce your overall downtime a bit.
Nah, part of the playbook sets up the initial Lets Encrypt certificate... so DNS needs to point to the new VPS. And the hostname needs to match the existing instance as it is referenced in the database.
Doesn't matter now anyway, I went a different route :)
How'd you end up migrating it?
I didn't, I spun up an entirely new instance.
view more: next ›