Overview
Caddy helps Better-PaaS route domains and automate HTTPS certificates. The integration keeps the platform workflow practical without hiding the underlying infrastructure from you.
Role in the workflow
Caddy is used to route domains and automate HTTPS certificates. It supports the broader Better-PaaS goal: deploy from source or image, run in containers, route traffic securely, and keep operations understandable.
Setup considerations
Configuration depends on the integration. Always verify credentials, network access, DNS, and app health before switching production traffic.
- Confirm credentials and permissions
- Check environment variables
- Inspect logs after setup
- Document any external dependency
Operational guidance
Treat integrations as part of your deployment system. Rotate secrets when needed, back up stateful services, and keep the server updated.
Integration setup tip
Caddy config is managed by the platform - avoid hand-editing Caddyfiles on the host unless you understand override risks.
FAQ
Is Caddy required for Better-PaaS?
Some integrations are core platform dependencies, while others are optional workflow integrations. The setup guide for each feature explains when it matters.
Can I use Caddy with custom Docker images?
Usually yes when the app image exposes the right port and accepts configuration through environment variables.