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

Adjust blank lines: remove duplicated ones

Browse Source 
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This commit is contained in:
Suguru Hirahara
2024-12-01 02:28:06 +09:00
parent bc1849d7ff
commit dd5881f2b8
70 changed files with 0 additions and 195 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/configuring-playbook-synapse-s3-storage-provider.md
View File

@ -4,7 +4,6 @@ If you'd like to store Synapse's content repository (`media_store`) files on Ama
An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md).
## How it works?
Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/).
@ -22,7 +21,6 @@ You can run some scripts to delete the local files once in a while (which we do
While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store.
## Installing
After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
@ -57,7 +55,6 @@ If you have existing files in Synapse's media repository (`/matrix/synapse/media
Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below.
## Migrating your existing media files to the S3 store
Migrating your existing data can happen in multiple ways: