Improve Caddyfile editor for demo-style configs
Publish Docker image / build (push) Failing after 6s

This commit is contained in:
Daniel committed 2026-05-03 18:59:32 +02:00
1 parent d672ad3f47
commit e9035bf6fe
7 files changed
+1130 -47

No files matched your search

+4 -2
View File
@@ -5,8 +5,8 @@ Web UI for managing an existing dockerized [Caddy](https://caddyserver.com/) ins
## Features
- **Structured editor** — separate panels for global options and each site block
- **Raw editor** — optional full Caddyfile editing escape hatch for advanced changes
- **Admin API check** — blocks editing if Caddy's admin API is unreachable on load
- **Admin API toggle** — one checkbox adds/removes `admin :2019` from global options
- **Upstream reachability check** — warns before deploy if any `reverse_proxy` target is unreachable, with option to deploy anyway
- **Atomic deploy** — posts config to Caddy's `/load` endpoint; bad configs are rejected without disrupting the running instance
@@ -76,9 +76,11 @@ On first load it imports your existing Caddyfile (read-only). After the first de
| Action | Description |
|--------|-------------|
| **Global Options** panel | Edit top-level Caddy options (email, logging, etc.) |
| **Enable Admin API** checkbox | Adds/removes `admin :2019` from global options |
| **Raw Caddyfile** mode | Edit the full Caddyfile directly; deploy still uses Caddy's admin API, so no restart is required |
| **+ Add Site** | Creates a new site block |
| **Remove** (per site) | Deletes that site block |
| **Deploy** | Validates and applies config via Caddy's `/load` API; shows errors inline if rejected |
If any `reverse_proxy` upstream is unreachable at deploy time, a warning modal lists them — you can cancel or deploy anyway.
Switching from raw mode back to structured mode reparses the file, so comments and exact formatting may be normalized.