Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Issue with synapse_config_path #4822

Closed
relink2013 opened this issue Mar 6, 2019 · 2 comments
Closed

Issue with synapse_config_path #4822

relink2013 opened this issue Mar 6, 2019 · 2 comments

Comments

@relink2013
Copy link

I'm not sure if there is an issue or if the process is just not well documented. But any time I set the environment variable SYNAPSE_CONFIG_PATH The container fails to start. I assume this is due to their not being a homeserver.yal file present, however you can't generate a config without the container running.

If you manually create a config file then the container just throws a bunch of non descriptive errors and stops.

If this is just user error can we get some clarification on how to properly set this up using a homeserver.yaml

@richvdh
Copy link
Member

richvdh commented Mar 6, 2019

You don't mention it but I assume you're trying to use the docker image.

however you can't generate a config without the container running.

you can generate a config by running the docker image with a generate argument. For example:

docker run -it --rm --name synapse -v ~/tmp/data:/data \
    -e SYNAPSE_CONFIG_PATH=/data/homeserver.yaml \
    -e SYNAPSE_SERVER_NAME=my.matrix.host \
    -e SYNAPSE_REPORT_STATS=yes \
    matrixdotorg/synapse:latest generate 

This doesn't seem to be documented, sadly. A PR to fix https://github.com/matrix-org/synapse/blob/develop/docker/README.md would be much appreciated.

If you manually create a config file then the container just throws a bunch of non descriptive errors and stops.

well, I suspect that the errors are descriptive, but your GUI is mangling them somehow.

@richvdh
Copy link
Member

richvdh commented Mar 7, 2019

docs now updated to include the generate option

@richvdh richvdh closed this as completed Mar 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants