Caddy config loading
After upgrading both CLI and machine daemons to v0.12.1, you can redeploy Caddy without using the --watch flag.
The Caddy config is now loaded automatically by the machine daemon via the Caddy Admin API. This allows to log errors and not overwrite the Caddyfile on disk if the config is invalid. uc caddy config should now return the latest config that was successfully loaded into Caddy.
Unique context name for new clusters
When creating a new cluster, if the default context name default is already taken, a unique name like default-1, default-2, etc. will be generated automatically.
Changelog
- 8358343 chore: Add GH bug report template
- 9963f9d chore: Update bug template
- 5baa808 chore: load Caddy config via admin API instead of watching Caddyfile change on fs
- d25864e feat: automatically generate a unique 'default-N' context name for new cluster (fixes #113)
- ec2787c fix: Handle implicit relative path for config
- 51ba3c7 fix: landing navbar on mobile
- 97bdb8e fix: skip validation for user-defined Caddy configs if caddy not running locally
- 7b88b8b fix: write generated Caddyfile to disk only if succesfully loaded into local Caddy (means valid)