"backend" in service's haproxy config is required, not documented about synapse HOT 5 CLOSED

bah, i'm a bad maintainer; @memory which arguments that normally go into listen can go into backend? can these be the same thing?

from synapse.

the matrix says no; now we're going to have duplication of config information between listen and backend sections. probably, as part of the changes to the config format, we should have dynamically build the listen directive.

i think we can do this by being a little smarter about what the different haproxy directives mean and which sections they can go in. then, we can extract the ones that relate to backend or frontend from listen and put them there without requiring an extra backend config section...

@memory does that sound like a reasonable approach?

from synapse.

Actually my original pass at this involved trying to build out the listen section a little more dynamically, but I went for the minimal-changes route.

from synapse.

In short: yes. :)

from synapse.

i think this is fixed now; closing

from synapse.