But that JSON config file?
It’s a mistake. And I’m Being charitable and nice here.
Especially the part where there is an api to update the JSON file.
Jesus Christ Matt. Just use the caddyfile already. It’s easy, easy to read by everyone. Why make a config file hard to grok or follow by multiple team members?
I don’t get that part.
Like Matt said, I don't understand the problem here. Just use the Caddyfile. What problem do you have with it specifically? If there's a feature you're missing or aren't sure how to use, open an issue or ask for help on the forums.
Also thanks for fixing the slow JSON schema docs pages, really helped a lot.
The docs pages took longer to make than the core of Caddy 2 did, so I'm glad you like those too and find them helpful. That performance fix was a breath of fresh air for me too.
Anyway, nice to hear from another happy JSON consumer. I know several large companies using the JSON exclusively as well.