Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why do you need caddy? #50

Open
AlexMikhalev opened this issue Dec 29, 2022 · 2 comments
Open

Why do you need caddy? #50

AlexMikhalev opened this issue Dec 29, 2022 · 2 comments

Comments

@AlexMikhalev
Copy link

Apologies for asking in issues:
Great project, but I was wondering why do you need caddy if you are using cloudflared tunnels?

@rounakdatta
Copy link
Owner

Thanks, and as you said, Caddy wasn't in my plan when I was starting, it came out as a convinence requirement for certain apps. Some apps like Vikunja, Immich have a microservices architecture, and hence each of these μservices are running as different containers. Caddy helps me in pinning these into a single port, via different routes. Like say /api for the backend, /web for the website and so on.

That way I'll be able to have only a single Cloudflare Tunnel which exposes that single port. Sure, the other option could also be multiple tunnels, like api.example.com pointing to :8081, web.example.com pointing to :8080 and so on. But I chose the former option.

Ref: https://github.com/rounakdatta/homelab.setup/blob/main/templates/Caddyfile.j2

@AlexMikhalev
Copy link
Author

Thank you for the great explanation. I am evaluating options for the same type of setup - between nginx, traefik and caddy. My preference would be none of them :-D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants