We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recreating caddy doesn't happen unless the container image gets updated. Which means config updates aren't reflected, unless Caddy gets manually restarted.
caddy should get restarted or have a reload on every config change
Relevant: https://caddyserver.com/docs/running#usage migrated from aosus/hyper-aosus#487
The text was updated successfully, but these errors were encountered:
Caddy --watch was suggested in matrix, however Caddy devs caution against using it in some use cases. https://caddy.community/t/why-is-caddy-run-watch-dangerous/8981
--watch
Sorry, something went wrong.
aosus/cups-1@f6ba8ee
No branches or pull requests
Recreating caddy doesn't happen unless the container image gets updated.
Which means config updates aren't reflected, unless Caddy gets manually restarted.
caddy should get restarted or have a reload on every config change
Relevant:
https://caddyserver.com/docs/running#usage
migrated from
aosus/hyper-aosus#487
The text was updated successfully, but these errors were encountered: