wweir 2988505770 fix(config): keep the checked-in sowerd example in sync with the embedded one ...

config/sowerd.toml and ExampleSowerdConfigTOML are the same artifact kept in
two places: the constant is what `sowerd -i` writes to /etc/sower/sowerd.toml
(internal/install/service.go), the file is what `-c config/sowerd.toml` loads
during development. They had drifted in both directions -- the constant
carried the [site_routes.routes] path-prefix example and the older cert.domains
wording, while the file carried the newer wording and left `domains`
uncommented -- so a deployment got guidance contradicting the shipped binary
depending on which copy it read.

Take the constant as the source of truth, comment out the placeholder
cert.domains entry (a placeholder domain is not one the operator owns) and pin
the two copies byte for byte with a test that prints the differing lines.

2026-10-10 14:56:49 +08:00

..

example_load_test.go

fix(config): keep the checked-in sowerd example in sync with the embedded one

2026-10-10 14:56:49 +08:00

sower_test.go

fix(install,config): lock down installed config, atomic binary copy, reject socks5 password, parse bare ipv6

2026-08-12 17:23:14 +08:00

sower.go

fix(install,config): lock down installed config, atomic binary copy, reject socks5 password, parse bare ipv6

2026-08-12 17:23:14 +08:00

sower.toml

fix(sower): keep the soft heap limit above the live rule heap

2026-09-18 22:37:03 +08:00

sowerd_test.go

feat(sowerd): support path-prefix routing within site routes

2026-08-13 08:44:38 +08:00

sowerd.go

fix(config): keep the checked-in sowerd example in sync with the embedded one

2026-10-10 14:56:49 +08:00

sowerd.toml

fix(config): keep the checked-in sowerd example in sync with the embedded one

2026-10-10 14:56:49 +08:00