Local HTTPS Proxy and Certs

Run multiple local services behind stable HTTPS domains for realistic local integration.

Recommended approach

Use Caddy as local reverse proxy and TLS certificate manager.

Example host mapping:

api.project.localhost -> localhost:3137
app.project.localhost -> localhost:5137
mailbox.project.localhost -> localhost:8025

Alternatives and when to choose them

Traefik if already used in local Docker setups.
No proxy for single-service local apps.

Implementation checklist

Keep proxy config in version control.
Standardize local domains across team.
Ensure one command starts all needed local services.

Common pitfalls

Port-only local setup causing onboarding friction.
Inconsistent cert trust setup across developer machines.

Monorepo Workspaces

Share code safely across frontend/backend/apps while preserving clear ownership.

Local Infra with Docker Compose

Provide local dependencies (database, cache, mail catcher) with consistent setup across the team.

On this page

Recommended approach Alternatives and when to choose them Implementation checklist Common pitfalls Related pages