Overview
Caddy Static Site Production Profile is a Caddy web server set up to serve static files with automatic HTTPS. This is a production-oriented profile of Caddy Static Site, with defaults geared toward stable, always-on operation rather than experimentation. On DockerCP it runs as a managed Docker container with persistent volumes, environment variables, domain routing, and one-click SSL. Once it is running, you can attach domains, issue SSL certificates, inspect logs, and monitor resource usage directly from the panel.
How deployment works in DockerCP
This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.
- Create or select a project where the service belongs.
- Review the Docker image, tag, default port, environment variables, and volume mappings.
- Deploy the service and check logs until the application is healthy.
- Attach a domain or subdomain when the application must be available publicly.
- Enable HTTPS and verify the final browser response.
Configuration
Environment variables
| Variable | Default / guidance |
|---|---|
APP_ENV |
production |
APP_PORT |
80 |
Persistent volumes
| Volume | Mount path |
|---|---|
| caddy_static_site_production_profile_data | /data |
Commands
DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence.
docker pull caddy:alpine
docker ps --filter "name=caddy-static-site-production-profile"
docker logs --tail=100 caddy-static-site-production-profile
DNS and SSL checklist
| Step | Expected result |
|---|---|
| Add A or CNAME record | The domain points to the DockerCP server or configured target. |
| Attach domain to service | The service is reachable through the selected hostname. |
| Enable HTTPS | The certificate becomes active and redirect to HTTPS can be enabled. |
Screenshots
Panel previews for the Caddy Static Site Production Profile template: how deployment, the running service, and its key details look inside DockerCP.
Run Caddy Static Site in a production profile tuned for steady, always-on traffic, a Caddy web server set up to serve static files with automatic HTTPS.
Troubleshoot
- Confirm the Docker image and tag exist.
- Confirm the selected internal port matches the application port.
- Confirm required variables such as database URL, app URL, and credentials are set.
- Check service logs after the first deployment.
- Verify DNS before requesting or renewing SSL certificates.