Caddy Fallback Server

This directory contains the docker-compose.yml for running a standalone Caddy server, potentially as a fallback or for specific local proxy needs.

Running with Podman Compose

To run this service using podman-compose:

Navigate to this directory:
```
cd optimized/standalone/Caddy
```
Ensure Caddyfile and maintenance.html exist in this directory as they are mounted as volumes.
Start the service:
```
podman-compose up -d
```

Running with Podman

You can run the Caddy service directly with Podman. Note that for proper function, the Caddyfile, maintenance.html, and volume mounts are crucial.

podman run -d \
  --name caddy_fallback \
  --restart unless-stopped \
  -p "8080:80" \
  -p "8443:443" \
  -v ./Caddyfile:/etc/caddy/Caddyfile \
  -v ./maintenance.html:/srv/maintenance/maintenance.html \
  -v caddy_data:/data \
  -v caddy_config:/config \
  -v caddy_logs:/var/log/caddy \
  caddy:latest

Notes

Ensure the Caddyfile and maintenance.html are configured correctly for your use case.
The Caddy service was categorized as standalone because Traefik is designated for Swarm ingress, implying Caddy has a specialized, non-Swarm role here.