Merge pull request #1043 from aaronraimist/patch-1
Tweak maintenance-synapse.md
This commit is contained in:
commit
ac8a9989aa
|
@ -14,11 +14,7 @@ Table of contents:
|
||||||
|
|
||||||
## Purging old data with the Purge History API
|
## Purging old data with the Purge History API
|
||||||
|
|
||||||
You can use the **Purge History API** to delete in-use (but old) data.
|
You can use the **[Purge History API](https://github.com/matrix-org/synapse/blob/master/docs/admin_api/purge_history_api.rst)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**.
|
||||||
|
|
||||||
**This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**.
|
|
||||||
|
|
||||||
Synapse's [Purge History API](https://github.com/matrix-org/synapse/blob/master/docs/admin_api/purge_history_api.rst) can be used to purge on a per-room basis.
|
|
||||||
|
|
||||||
To make use of this API, **you'll need an admin access token** first. You can find your access token in the setting of some clients (like Element).
|
To make use of this API, **you'll need an admin access token** first. You can find your access token in the setting of some clients (like Element).
|
||||||
Alternatively, you can log in and obtain a new access token like this:
|
Alternatively, you can log in and obtain a new access token like this:
|
||||||
|
@ -29,6 +25,8 @@ curl \
|
||||||
https://matrix.DOMAIN/_matrix/client/r0/login
|
https://matrix.DOMAIN/_matrix/client/r0/login
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Synapse's Admin API is not exposed to the internet by default. To expose it you will need to add `matrix_nginx_proxy_proxy_matrix_client_api_forwarded_location_synapse_admin_api_enabled: true` to your `vars.yml` file.
|
||||||
|
|
||||||
Follow the [Purge History API](https://github.com/matrix-org/synapse/blob/master/docs/admin_api/purge_history_api.rst) documentation page for the actual purging instructions.
|
Follow the [Purge History API](https://github.com/matrix-org/synapse/blob/master/docs/admin_api/purge_history_api.rst) documentation page for the actual purging instructions.
|
||||||
|
|
||||||
After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql).
|
After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql).
|
||||||
|
@ -36,7 +34,7 @@ After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintena
|
||||||
|
|
||||||
## Compressing state with rust-synapse-compress-state
|
## Compressing state with rust-synapse-compress-state
|
||||||
|
|
||||||
[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse.
|
[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database.
|
||||||
|
|
||||||
This tool should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first.
|
This tool should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first.
|
||||||
|
|
||||||
|
@ -54,7 +52,10 @@ After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./main
|
||||||
|
|
||||||
## Browse and manipulate the database
|
## Browse and manipulate the database
|
||||||
|
|
||||||
When the [matrix admin API](https://github.com/matrix-org/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs.
|
When the [Synapse Admin API](https://github.com/matrix-org/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs.
|
||||||
|
|
||||||
|
Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql).
|
||||||
|
|
||||||
First, set up an SSH tunnel to your matrix server (skip if it is your local machine):
|
First, set up an SSH tunnel to your matrix server (skip if it is your local machine):
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in a new issue