Lemmy

12514 readers

111 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

nutomic@lemmy.ml

Instance relocation (lemmy.click)

submitted 1 year ago* (last edited 1 year ago) by Lodion@lemmy.click to c/lemmy@lemmy.ml

4 comments fedilink hide all child comments

I'm planning to move my instance to a new VPS provider that will allow me to scale more simply.

Has anyone done this already and can sanity check my plan? My current setup was spun up using the ansible playbook here.

Current plan is:

Lower DNS TTL to 60 seconds (already done)

Shutdown on current VPS: docker-compose down

backup /srv/lemmy// and copy to new host

sudo tar -zcvpf backup.tar.gz /srv/lemmy//

scp backup.tar.gz user@newhost

update dns A and AAAA records, wait 1 minute, verify DNS has updated

run ansible script

Shutdown on new VPS: docker-compose down

restore backup to /srv/lemmy//

Startup on new VPS with restored DB etc: docker-compose up -d

test

destroy old VPS

Increase DNS TTL to 86400

Anything I've missed? :)

top 4 comments

sorted by: hot top controversial new old

[–] drk@slrpnk.net 0 points 1 year ago (1 children)

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.

[–] Lodion@lemmy.click 0 points 1 year ago (1 children)

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 :)

[–] kiwi@lemmy.one 1 points 1 year ago (1 children)

How'd you end up migrating it?

[–] Lodion@lemmy.click 1 points 1 year ago

I didn't, I spun up an entirely new instance.