Repository files, collaboration, releases and project activity.
ARCHFORGE HISTORY
Blame · CHANGELOG-1.0.2.md
Branch main · the Commit author is not necessarily a verified ArchForge account.
b8619f148earchadmin2026-10-11
1 # ArchForge External Status 1.0.2 — Domain & TLS Setupb8619f148earchadmin2026-10-11
2 b8619f148earchadmin2026-10-11
3 - New `configure-domain.sh` wizard for **existing Debian 13 installations**. Run from the cloned Git repository after deploying changes to ArchForge Git.b8619f148earchadmin2026-10-11
4 - Guides DNS A/AAAA, public VPS IP matching, optional ACME email and firewall considerations.b8619f148earchadmin2026-10-11
5 - Creates/updates just `/etc/caddy/conf.d/archforge-status.caddy` and `STATUS_PUBLIC_URL`, without touching secrets, database or admin.b8619f148earchadmin2026-10-11
6 - Uses `caddy validate`, systemd reload and attempts verified HTTPS `/healthz`; accurately says **pending** if the actual TLS certificate has not yet been verified.b8619f148earchadmin2026-10-11
7 - Restores the original Caddy configuration, status.env and app public URL on validation or restart failure.b8619f148earchadmin2026-10-11
8 - New isolated DNS/domain/env unit tests; keeps original admin recovery and monitoring functions unchanged.b8619f148earchadmin2026-10-11
9 - No updates to the main ArchForge website or its Git server.