Hard to follow upstream homserver.yaml? #33
Closed
opened 2022-07-15 14:08:09 +00:00 by decentral1se
·
3 comments
No Branch/Tag Specified
main
renovate/matrixdotorg-synapse-1.x
renovate/ghcr.io-element-hq-matrix-authentication-service-1.x
renovate/dock.mau.dev-mautrix-telegram-0.x
newmain3
upgrade-7.2.0+v1.154.0
upgrade-7.2.1+v1.155.0
compress-and-federate2
renovate/postgres-18.x
chore/meet.wiki.cafe-deployment
fix/3wc/server-name
compress-and-federate
add-matrix-authentication-service
feat/3wc/caddy
compress
feature/add-qr-login
6.8.1fix
auto_join_room_list
auto-join-rooms
cas_expose_maxupload
old-signing-key
added-env-vars
addtional-env-vars
homeserver-config-updates
backupbot
serve_server_wellknown
coturn
7.3.1+v1.157.1
7.3.0+v1.155.0
7.2.1+v1.155.0
7.2.0+v1.154.0
7.1.1+v1.149.1
7.1.0+v1.149.1
7.0.2+v1.149.1
7.0.1+v1.149.1
7.0.0+v1.149.1
6.8.3+v1.139.2
6.8.2+v1.139.2
6.8.1+v1.139.2
6.8.0+v1.139.2
6.7.1+v1.133.0
6.7.0+v1.133.0
6.6.3+v1.124.0
6.6.2+v1.124.0
6.6.1+v1.124.0
6.6.0+v1.124.0
6.5.0+v1.117.0
6.4.0+v1.116.0
6.3.0+v1.113.0
6.2.0+v1.113.0
6.1.4+v1.112.0
6.1.3+v1.111.1
6.1.2+v1.111.0
6.1.1+v1.110.0
6.1.0+v1.110.0
5.0.6+v1.100.0
6.0.2+v1.100.0
6.0.1+v1.100.0
6.0.0+v1.100.0
5.0.5+v1.100.0
5.0.5+1.25.3
5.0.4+v1.100.0
5.0.3+v1.100.0
5.0.2+v1.93.0
5.0.1+v1.93.0
5.0.0+v1.93.0
4.0.0+v1.93.0
3.9.1+v1.87.0
3.9.0+v1.87.0
3.8.0+v1.84.1
3.7.0+v1.82.0
3.6.0+v1.81.0
3.5.0+v1.81.0
3.4.0+v1.80.0
3.3.0+v1.78.0
3.2.0+v1.77.0
3.1.0+v1.76.0
3.0.0+v1.74.0
2.6.0+v1.74.0
2.5.0+v1.73.0
2.4.0+v1.72.0
2.3.0+v1.71.0
2.2.0+v1.68.0
2.1.0+v1.62.0
2.0.0+v1.58.1
1.3.0+v1.55.2
1.2.0+v1.52.0
1.1.0+v1.51.0
1.0.1+1.48.0
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/matrix-synapse#33
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 @sef! 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.