8 commits

Author	SHA1	Message	Date
Mark Felder	1e5fec8d45	Ask user to use matching values for database setup	2020-10-09 09:14:02 -05:00
Mark Felder	e0c5adcc20	Syntax error	2020-10-08 15:56:37 -05:00
Mark Felder	5f38e03c8a	Don't always need to drop	2020-10-08 15:54:28 -05:00
Mark Felder	a02ed3920f	Improve backup/restore documentation	2020-10-08 15:51:56 -05:00
lain	c05cbc47f9	Better advice for vacuuming after restoring.	2020-02-22 13:14:30 +00:00
Igeljäger	1ed485ec1d	added why doing a vacuum after restoring a backup is so important	2020-02-21 15:30:52 +00:00
Ilja	a9e946b99a	DOCS Backup/Restore/Migrate your instance ... * Added "Migrate" to the title because these steps can also be used to migrate the instance to another server * Added an optional step to reinstall pleroma (esp. for migrating servers) * Currently the steps threw an error 'could not execute query: ERROR: function "activity_visibility already exists with the same argument types' * I added a new step to drop and recreate an empty pleroma-database * I played around with the `-c` and `-C` options of pg_restore, but dropping and recreating seemd to be the only way I got it working * This was tested on Debian Stretch, psql (PostgreSQL) 9.6.15	2020-02-10 23:53:26 +00:00
rinpatch	acc62f327d	Rename some directories because MkDocs uses them for categories	2019-10-02 23:28:45 +03:00

Renamed from docs/admin/backup.md (Browse further)