Get the IP and set up the dns for the new server. Get a cert via Let’s Encrypt or self sign to get ssl working, and then start your prep.
On the new host create the new directory structure. Note your folders, paths, and permissions. Set the permissions on the pictrs folder as 991 (sudo chown 991:991 /path/to/pictrs/folder even if that user doesn’t exist on your system. It’s for the container.
You’ll need to edit your yml files, docker compose file, and make sure that the paths are updated, the instance name is correct, and federation is disabled (until testing is done).
Copy pictrs and db folders from old host to new. You can skip pictrs if space is a concern, but you’ll lose your instance pics.
Once done, copy over the containers and bring them up.
Check for errors and diagnose as necessary.
Once set, change the federation to on, switch your dns from old server to new, and then perform another sanity test.
Just to clarify: will you use the same domain? If yes, oleorun’s answer is good enough. If not, it would be much more harder (you would also have to update your instance’s URL and users’ inboxes URLs in the database for federation to work, probably have to unsubscribe aand resubscribe to every community on your instance and even then I’m not sure that would not lead to federation issues)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
deleted by creator
Here’s a quick method:
Get the IP and set up the dns for the new server. Get a cert via Let’s Encrypt or self sign to get ssl working, and then start your prep.
On the new host create the new directory structure. Note your folders, paths, and permissions. Set the permissions on the pictrs folder as 991 (sudo chown 991:991 /path/to/pictrs/folder even if that user doesn’t exist on your system. It’s for the container.
You’ll need to edit your yml files, docker compose file, and make sure that the paths are updated, the instance name is correct, and federation is disabled (until testing is done).
Copy pictrs and db folders from old host to new. You can skip pictrs if space is a concern, but you’ll lose your instance pics.
Once done, copy over the containers and bring them up.
Check for errors and diagnose as necessary.
Once set, change the federation to on, switch your dns from old server to new, and then perform another sanity test.
Just to clarify: will you use the same domain? If yes, oleorun’s answer is good enough. If not, it would be much more harder (you would also have to update your instance’s URL and users’ inboxes URLs in the database for federation to work, probably have to unsubscribe aand resubscribe to every community on your instance and even then I’m not sure that would not lead to federation issues)