finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Do not refer to Synapse as "Matrix Synapse"

Browse Source
This commit is contained in:
Slavi Pantaleev
2019-04-23 10:20:56 +03:00
parent 39566aa7fe
commit 892abdc700
11 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/configuring-playbook-s3.md
View File

@ -1,9 +1,9 @@
# Storing Matrix media files on Amazon S3 (optional)
By default, this playbook configures your server to store Matrix Synapse's content repository (`media_store`) files on the local filesystem.
By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem.
If that's alright, you can skip this.
If you'd like to store Matrix Synapse's content repository (`media_store`) files on Amazon S3,
If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3,
you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you.
You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example security policy:
@ -36,4 +36,4 @@ matrix_s3_media_store_bucket_name: "your-bucket-name"
matrix_s3_media_store_aws_access_key: "access-key-goes-here"
matrix_s3_media_store_aws_secret_key: "secret-key-goes-here"
matrix_s3_media_store_region: "eu-central-1"
```
```

4
docs/importing-media-store.md
View File

@ -1,6 +1,6 @@
# Importing `media_store` data files from an existing installation (optional)
Run this if you'd like to import your `media_store` files from a previous installation of Matrix Synapse.
Run this if you'd like to import your `media_store` files from a previous installation of Synapse.
## Prerequisites
@ -19,4 +19,4 @@ Run this command (make sure to replace `<server-path-to-media_store>` with a pat
ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_media_store=<server-path-to-media_store>' --tags=import-media-store
**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!).
**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!).

2
docs/importing-postgres.md
View File

@ -1,6 +1,6 @@
# Importing an existing Postgres database from another installation (optional)
Run this if you'd like to import your database from a previous installation of Matrix Synapse.
Run this if you'd like to import your database from a previous installation of Synapse.
(don't forget to import your `media_store` files as well - see [the importing-media-store guide](importing-media-store.md)).

8
docs/importing-sqlite.md
View File

@ -1,12 +1,12 @@
# Importing an existing SQLite database from another installation (optional)
Run this if you'd like to import your database from a previous default installation of Matrix Synapse.
Run this if you'd like to import your database from a previous default installation of Synapse.
(don't forget to import your `media_store` files as well - see [the importing-media-store guide](importing-media-store.md)).
While this playbook always sets up PostgreSQL, by default a Matrix Synapse installation would run
While this playbook always sets up PostgreSQL, by default a Synapse installation would run
using an SQLite database.
If you have such a Matrix Synapse setup and wish to migrate it here (and over to PostgreSQL), this command is for you.
If you have such a Synapse setup and wish to migrate it here (and over to PostgreSQL), this command is for you.
## Prerequisites
@ -20,4 +20,4 @@ Run this command (make sure to replace `<server-path-to-homeserver.db>` with a f
ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_homeserver_db=<server-path-to-homeserver.db>' --tags=import-sqlite-db
**Note**: `<server-path-to-homeserver.db>` must be a file path to a `homeserver.db` file on the server (not on your local machine!).
**Note**: `<server-path-to-homeserver.db>` must be a file path to a `homeserver.db` file on the server (not on your local machine!).