Simplify Caddy infrastructure to use file-based configuration instead of complex API registration system

This commit is contained in:
2025-11-15 00:11:46 +01:00
parent 7788410bfc
commit 8162e789ee
13 changed files with 706 additions and 216 deletions

View File

@@ -18,20 +18,22 @@ cloudflare_api_token: "{{ vault_cloudflare_api_token }}"
caddy_acme_ca: "https://acme-v02.api.letsencrypt.org/directory"
# =================================================================
# Site Configuration
# API Service Registration Configuration
# =================================================================
# For now, just serve the main jnss.me domain
# Additional sites can be added here as services are deployed
caddy_sites: []
# Services now self-register using Caddy's admin API
caddy_api_enabled: true
caddy_server_name: "main"
# Future sites will look like:
# caddy_sites:
# - domain: "cloud.jnss.me"
# backend: "localhost:8080"
# dns_challenge: true
# - domain: "auth.jnss.me"
# backend: "localhost:9000"
# dns_challenge: true
# Static site configuration is deprecated - use API registration instead
# Services should use the registration handlers:
#
# Example service registration pattern:
# - name: Register my service
# set_fact:
# service_name: "myapi"
# service_domain: "api.jnss.me"
# service_backend: "localhost:8080"
# notify: register service with caddy
# =================================================================
# Security & Logging