Commit Graph

10 Commits

Author SHA1 Message Date
Suguru Hirahara
174b18be9a
Fix capitalization: id → ID
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
2024-10-16 02:25:03 +09:00
Slavi Pantaleev
6c3746b237 Update migrating guide to make it clear that switching CPU architecture requires skipping /matrix/postgres/data 2024-07-08 07:33:50 +03:00
chagai95
8ba1e771b9
Add a small tip to maintenance-migrating.md 2023-08-30 10:00:32 +02:00
Slavi Pantaleev
c791d1900c
Improve wording 2021-05-26 18:03:47 +03:00
WobbelTheBear
54e1c67e53
Update maintenance-migrating.md 2021-05-26 16:31:01 +02:00
WobbelTheBear
8472848286
Annotate server migration
Annotate server migration with a note in regard to migration between different architectures and the need to dump/restore the database.
2021-05-26 16:30:08 +02:00
chagai95
07fb05a4ab
fix typo
ot -> to
2021-03-17 20:29:17 +01:00
Slavi Pantaleev
ccc7aaf0ce Fix "Migrating to a new server" flow due to dynamic user/group creation 2020-05-06 09:55:40 +03:00
Slavi Pantaleev
8a7b3d5bd0
Make instructions simpler and safer
Changes to the original are:
- it tells people to stop and disable services, so that:
   - services won't be running while you are copying files
   - services won't accidentally start again later
- it does the file-copying in 1 step
- it does copying before running `--tags=setup-all`, so that existing files (SSL certificates, etc.) can be reused. Otherwise, the playbook starts from a blank slate, retrieves them anew, generates new signing keys anew, etc. Only to have those replaced by your own old backup later.
- it mentions DNS changes
- combines `--tags=setup-all,start` into a single step, thanks to the files being already copied
2019-06-12 09:36:19 +03:00
Michael Haak
a8dc0befa9 Added a basic guide on migrating to another server 2019-06-11 22:06:25 +02:00