Fix "Migrating to a new server" flow due to dynamic user/group creation
This commit is contained in:
		| @@ -5,4 +5,6 @@ | |||||||
| 3. Copy directory `/matrix` from the old server to the new server. Make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)! | 3. Copy directory `/matrix` from the old server to the new server. Make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)! | ||||||
| 4. Make sure your DNS records are adjusted to point to the new server's IP address | 4. Make sure your DNS records are adjusted to point to the new server's IP address | ||||||
| 5. Remove old server from the `inventory/hosts` file and add new server. | 5. Remove old server from the `inventory/hosts` file and add new server. | ||||||
| 6. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`. This will create the matrix user and group and start all services on the new server | 6. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user`. This will create the `matrix` user and group on the new server | ||||||
|  | 7. Because the `matrix` user and group are created dynamically on each server, the user/group id may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files manually by running this on the new server: `chown -R matrix:matrix /matrix`. | ||||||
|  | 8. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` to finish the installation and start all services | ||||||
|   | |||||||
| @@ -18,6 +18,7 @@ | |||||||
|   when: run_setup|bool |   when: run_setup|bool | ||||||
|   tags: |   tags: | ||||||
|     - always |     - always | ||||||
|  |     - setup-system-user | ||||||
|  |  | ||||||
| - import_tasks: "{{ role_path }}/tasks/setup_matrix_base.yml" | - import_tasks: "{{ role_path }}/tasks/setup_matrix_base.yml" | ||||||
|   when: run_setup|bool |   when: run_setup|bool | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user