Mastodon<\/a> is a microblogging platform akin to others you may have seen, such as Twitter, but instead of being centralised it is a federated network which operates in a similar way to email.<\/p>\n Like email, you choose your server and whether it\u2019s GMail, Outlook, iCloud, wherever you sign up you know you\u2019ll be able to email everyone you need to so long as you know their address.<\/p>\n The word \u201cinstance\u201d is often used on Mastodon as a synonym of server.<\/p>\n This means there\u2019s no big uncaring company running it all, no shareholders, no central control, none of the targeted advertising we\u2019re all fed up with, just a bunch of people sharing the things they want to share with each other.<\/p>\n (from https:\/\/blog.joinmastodon.org\/2018\/08\/mastodon-quick-start-guide\/<\/a>)<\/p>\n This Guide will show you how to migrate an existing Mastodon dockerized instance to a new Server without docker. Please read the complete Guide carefully before you start to migrate and if possible test it before live migration. I assume that Mastodon is running in the directory You have to stop the following containers manually, The following command will put the dump into the directory Wait a moment and then check if dump was created:<\/p>\n Then stop the complete stack with:<\/p>\n If you\u2019re using S3, you can skip this step. Otherwise use You copy the file now you have to adjust the settings for the database in and set Before importing the database, we have to copy the dump and create an empty Database on the new server:<\/p>\n change to user mastodon and create the empty DB:<\/p>\n Then import the dump:<\/p>\n Before we can start the new server, we have to precompile the assets as user then we rebuild the home timelines for our users:<\/p>\n This can take some time, when finished it is time to start the new server<\/p>\n You have to change your prompt back to user you can check the services with:<\/p>\n Do not forget to update your DNS settings to point to the new server and update or copy your Enjoy your new Server and disable the old one.<\/p>\n If you want to run your own fully managed Instance hosted in Germany with 100% green Energy, look here<\/a><\/p>\n If you want to use mastodon without your own instance you may register here:<\/p>\n MastodonTech.de<\/a><\/p>\n or here:<\/p>\n dresden.network<\/a><\/p>\n If you want to contribute to the running costs of this Blog or the running Mastodon-Instances, then you can use the following link:<\/p>\n Support<\/a><\/p>\n Thx and feel free to contact me \ud83d\ude42<\/p>\n ———–<\/p>\n Sources:<\/h3>\n
What is this Guide?<\/h3>\n
\nYou can also synchronize the files more than once to reduce the time required for live migration. The Installation on the new server without docker is documented here<\/a>. but don\u2019t run mastodon:setup.<\/p>\n<\/h6>\n
Requirements:<\/h6>\n
\n
<\/h5>\n
<\/h5>\n
On the old Server<\/h5>\n
~\/mastodon\/<\/code>, otherwise please adjust in the commands. The container names also depend on the directory-name.<\/p>\nStep 1: Stop Mastodon<\/h6>\n
mastodon_streaming_1<\/code>, mastodon_sidekiq_1<\/code> and mastodon_web_1<\/code>:<\/p>\ndocker stop mastodon_streaming_1 && docker stop mastodon_sidekiq_1 && docker stop mastodon_web_1<\/pre>\n
<\/h6>\n
Step 2: Create Database dump<\/h6>\n
~\/mastodon\/postgres\/<\/code><\/p>\ndocker exec mastodon_db_1 pg_dump -Fc -U postgres -d postgres -f mastodon.dump<\/pre>\n
ls -lah ~\/mastodon\/postgres\/<\/pre>\n
docker-compose down<\/pre>\n
<\/h5>\n
On the new Server<\/h5>\n
<\/h6>\n
Step 3: Sync system-files<\/h6>\n
rsync<\/code> to copy the files to your new server, I assume you use mastodon as user.<\/p>\nrsync -avz --chown=mastodon:mastodon --progress old.server.tld:~\/mastodon\/public\/system\/ ~\/mastodon\/live\/public\/system\/<\/pre>\n
<\/h6>\n
Step 4: Copy and Edit Configuration<\/h6>\n
.env.production<\/code> to your new server:<\/p>\nscp old.server.tld:\/~\/mastodon\/.env.production \/home\/mastodon\/live\/\r\nchown mastodon:mastodon \/home\/mastodon\/live\/.env.production<\/pre>\n
.env.production<\/code><\/p>\nnano \/home\/mastodon\/live\/.env.production<\/pre>\n
DB_SETTINGS<\/code>:<\/p>\nDB_HOST=\/var\/run\/postgresql\r\nDB_NAME=mastodon\r\nDB_USER=mastodon<\/pre>\n
<\/h6>\n
Step 5: Copy and Import database<\/h6>\n
scp old.server.tld:\/~\/mastodon\/postgres\/mastodon.dump \/tmp\/\r\nchown mastodon:mastodon \/tmp\/mastodon.dump<\/pre>\n
su - mastodon\r\ncreatedb -T template0 mastodon<\/pre>\n
pg_restore -U mastodon -n public --no-owner --role=mastodon -d mastodon \/tmp\/mastodon.dump<\/pre>\n
<\/h6>\n
Step 6: Finish the migration<\/h6>\n
mastodon<\/code>:<\/p>\ncd \/home\/mastodon\/live\/\r\nRAILS_ENV=production bundle exec rails assets:precompile<\/pre>\n
RAILS_ENV=production .\/bin\/tootctl feeds build<\/pre>\n
<\/h6>\n
Step 7: Start Mastodon<\/h6>\n
root<\/code> and start the services:<\/p>\nsystemctl start mastodon-sidekiq mastodon-streaming mastodon-web<\/pre>\n
systemctl status mastodon-sidekiq mastodon-streaming mastodon-web<\/pre>\n
Nginx\/Apache2 configuration<\/code>, re-run LetsEncrypt as necessary.<\/p>\n
\n
\nhttps:\/\/docs.joinmastodon.org<\/a><\/p><\/blockquote>\n