Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config file values need explanation #101

Open
anoadragon453 opened this issue Feb 11, 2019 · 4 comments
Open

Config file values need explanation #101

anoadragon453 opened this issue Feb 11, 2019 · 4 comments

Comments

@anoadragon453
Copy link
Member

Currently the config file is a bit of a mess. It has a collection of "default" values, but this is not the complete list of values. They are in an odd order (email things are not together for instance), and figuring out what each value does requires looking in the code (and there are no examples anywhere).

Ideally we'd have explanations in the generated config file, similar to Synapse, with examples for each one, and it would be organised better (correct ordering).

This isn't that hard, but someone needs to go ahead and do it, else every time someone sets up a Sydent dev environment they spent a couple hours figuring out how the config file works.

@richvdh
Copy link
Member

richvdh commented Mar 2, 2020

this. so much this.

@richvdh
Copy link
Member

richvdh commented Mar 9, 2022

Ideally we'd have explanations in the generated config file

Ideally we wouldn't generate a config file at all, imho. It is always going to be a poor substitute for actual documentation.

@Cyberes
Copy link

Cyberes commented Mar 29, 2022

From #512:

I see that I indeed set server.name in the Sydent config to example.com rather than sydent.example.com. When I configured it I wasn't sure if server.name was supposed to be the Synapse's server name (which would be example.com) or Sydent's host. Can the configuration docs be updated to include a little snippet about this distinction?

@felipeavilis
Copy link
Contributor

UP! I'd really like this documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants