From 8cd327dfebb515db200327a6d7a2363e1c11b2ea Mon Sep 17 00:00:00 2001 From: tsmethurst Date: Wed, 8 Sep 2021 14:24:47 +0200 Subject: [PATCH] start backup/restore doc --- docs/admin/backup_and_restore.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 docs/admin/backup_and_restore.md diff --git a/docs/admin/backup_and_restore.md b/docs/admin/backup_and_restore.md new file mode 100644 index 000000000..bd2b4b14a --- /dev/null +++ b/docs/admin/backup_and_restore.md @@ -0,0 +1,18 @@ +# Backup and Restore + +In certain conditions, it may be desirable to be able to back up a GoToSocial instance, and then to restore it again later, or just save the backup somewhere. + +Some potential scenarios: + +* You want to close down your instance but you might create it again later and you don't want to break federation. +* You need to migrate to a different database for some reason (Postgres => SQLite or vice versa). +* You want to keep regular backups of your data just in case something happens. +* You want to migrate from GoToSocial to a different Fediverse server, or from a different Fediverse server to GoToSocial. +* You're about to hack around on your instance and you want to make a quick backup so you don't lose everything if you mess up. + +There are a few different ways of doing this, most of which require some technical knowledge. + +## Image your disk + +If you're running GoToSocial on a VPS (a remote machine in the cloud), the easiest way to preserve all of your database entries and media is to .......................................... +