Hard to follow upstream homserver.yaml? #33
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Related to #32, I've seen that in https://github.com/matrix-org/synapse/pull/12941 they've removed all the new options from the
sample_config.ymlin new releases.This means, it is not possible to check all the
homeserver.yamlconfiguration changes and therefore adapt to new changes viagit log .... Especially for security changes.It seems that we now have to follow the change log and then look into each PR, to see what is the name / default of the new option? Does anyone have any tips here? I'm not quite sure how to keep up now.
I've just released 1.62.0 and it deployed find. But maybe some default config is on that shouldn't be? Feels a bit unstable now tbh.
/cc @yksflip @kawaiipunk
Perhaps the package maintenance commit log of Cloudron's Synapse can be of some use? https://git.cloudron.io/cloudron/synapse-app/-/commits/master
Nice @josef! I see they are doing a stripped config (no comments, no random defaults) in https://git.cloudron.io/cloudron/synapse-app/-/blob/master/homeserver.yaml.template which we could also consider, I guess. But the concerns in https://github.com/matrix-org/synapse/pull/12941 still apply, some defaults might flip from true/false and we wouldn't really know unless we're following the change log + commit log of upstream closely... there might be no way around that for now until upstream change the way theyre doing things?
Ping: I am gonna make a move on this soon-ish. If upstream is reducing the config size, I'm inclined to follow them. Then we use our collective brain on the recipe side to make good decisions for privacy and such as we go forward with it.