This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Update docker documentation #3222
Merged
neilisfragile
merged 4 commits into
develop
from
michaelkaye/update_docker_documentation
May 18, 2018
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
# Synapse Docker | ||
|
||
This Docker image will run Synapse as a single process. It does not provide any | ||
database server or TURN server that you should run separately. | ||
The `matrixdotorg/synapse` Docker image will run Synapse as a single process. It does not provide a | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. wrapping |
||
database server or a TURN server, you should run these separately. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. s/,/;/ or better yet rephrase it |
||
|
||
If you run a Postgres server, you should simply have it in the same Compose | ||
If you run a Postgres server, you should simply include it in the same Compose | ||
project or set the proper environment variables and the image will automatically | ||
use that server. | ||
|
||
|
@@ -37,10 +37,15 @@ then run the server: | |
docker-compose up -d | ||
``` | ||
|
||
If secrets are not specified in the environment variables, they will be generated | ||
as part of the startup. Please ensure these secrets are kept between launches of the | ||
Docker container, as their loss may require users to log in again. | ||
|
||
### Manual configuration | ||
|
||
A sample ``docker-compose.yml`` is provided, including example labels for | ||
reverse proxying and other artifacts. | ||
reverse proxying and other artifacts. The docker-compose file is an example, | ||
please comment/uncomment sections that are not suitable for your usecase. | ||
|
||
Specify a ``SYNAPSE_CONFIG_PATH``, preferably to a persistent path, | ||
to use manual configuration. To generate a fresh ``homeserver.yaml``, simply run: | ||
|
@@ -111,8 +116,6 @@ variables are available for configuration: | |
* ``SYNAPSE_SERVER_NAME`` (mandatory), the current server public hostname. | ||
* ``SYNAPSE_REPORT_STATS``, (mandatory, ``yes`` or ``no``), enable anonymous | ||
statistics reporting back to the Matrix project which helps us to get funding. | ||
* ``SYNAPSE_MACAROON_SECRET_KEY`` (mandatory) secret for signing access tokens | ||
to the server, set this to a proper random key. | ||
* ``SYNAPSE_NO_TLS``, set this variable to disable TLS in Synapse (use this if | ||
you run your own TLS-capable reverse proxy). | ||
* ``SYNAPSE_ENABLE_REGISTRATION``, set this variable to enable registration on | ||
|
@@ -132,6 +135,8 @@ Shared secrets, that will be initialized to random values if not set: | |
|
||
* ``SYNAPSE_REGISTRATION_SHARED_SECRET``, secret for registrering users if | ||
registration is disable. | ||
* ``SYNAPSE_MACAROON_SECRET_KEY`` secret for signing access tokens | ||
to the server. | ||
|
||
Database specific values (will use SQLite if not set): | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please please please can we wrap at 80 chars!