-
Notifications
You must be signed in to change notification settings - Fork 269
Description
Required check list:
- I didn't find in the repository's issues section a similar bug.
- I understand, this is an Open Source and not-for-profit product.
- This is not about a third-party project, framework, or technology.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the issue is.
Currently, cgapp supports Traefik and Nginx as reverse proxy options, but does not offer support for Caddy. This limits users who prefer Caddy’s simpler configuration, automatic HTTPS, and modern defaults, especially for local development and small to medium deployments.
As a result, developers who want to use Caddy must manually modify the generated setup after project creation, which breaks the “out-of-the-box” experience that cgapp provides.
Describe the solution you'd like:
A clear and concise description of what you want to happen.
Add first-class support for Caddy as an alternative reverse proxy option in cgapp, similar to existing Traefik and Nginx integrations. This could include:
- A Caddy option during project scaffolding
- Generated Caddyfile with sensible defaults
- Docker / Docker Compose integration consistent with existing setups
- HTTPS support (especially for local development) aligned with Caddy best practices
Describe alternatives you've considered:
A clear and concise description of any alternative solutions.
- Manually replacing Nginx or Traefik with Caddy after project generation
- Maintaining a custom fork or scripts to inject Caddy support