view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I'm open to using sothing like caddy or traefic, but my issue is I have a mix of packages hosted directly on system and in docker container's and as such need to proxy them all.
That's why I'm not using caddy or traefic.
Edit: rn my mix consists of about 16 diff containeraized stuff and another 4-5 not containerized stuff.
Edit2: Just now realized that they can be used on the host system's also. Would you recommend traefic or caddy?
If all was containerised, I'd recommend traefik for its impeccable container integration, but for a mix of bare metal and container services I'd go with Caddy.
I'm using Caddy (sometimes in a container or most of the time as system package) as reverse proxy mostly for containers
I try to minimize non-container services but they work well with Caddy too
Traefik is a tad more complex (still nowhere near Apache2 levels though) but scales more easily espcially if you only run containers and start/stop them programatically