Selfhosted

40329 readers

388 users here now

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Caddy > Traefik > NPM (self.selfhosted)

submitted 1 year ago* (last edited 1 year ago) by qwacko to c/selfhosted@lemmy.world

34 comments fedilink hide all child comments

Come on and fight me.....

I just tried out caddy for the first time and found it to be fantastic, I have used both Traefik and Nginx Proxy Manager extensively and although they were both great, the simplicity of the Caddfilr is fantastic. With a few snippets configured, I can add a host with a single line that just defines the port and url, it's like magic.

Has anyone got any known traps ( or tips) with caddy to make it useful.

The issues I have had previously with Traefik were the need to have multiplelines to configure it (and configure the host and router separately), and the difference between local docker services ( I do like using labels to configure, but with lots of services it gets a bit fragmented and difficult toanahe) and remote services ( had to use the file config).

With NPM, I find using the GUI to configure the servers difficult ( and challenging to keep consistent ) and I had a time that it forgot something ( can't remember if it was certificates or something else ) and that was the straw that broke the camel's back for me.

Anyway, currently I am happy with caddy and am not planning on replacing it (at least for a month or two :D ). It would be nice if there was a GUI, but no big drama honestly, and the text config is great.

you are viewing a single comment's thread
view the rest of the comments

[–] karlthemailman@sh.itjust.works 2 points 1 year ago* (last edited 1 year ago) (2 children)

Completely a personal preference, but this is one reason I prefer caddy. I like to keep the configs separate and not clutter up my compose files.

It means I need to update two things when adding a new service (a compose file plus my caddy file), but I like the separation of concerns.

It also makes my proxy config consistent for all services, regardless of whether that run in docket or elsewhere.

[–] Edo78@feddit.it 1 points 1 year ago (1 children)

I just use dockerized service and I plan to move to k8s so I don't have (nor plan to) deal with anything besides dockerized services

[–] karlthemailman@sh.itjust.works 2 points 1 year ago

Yeah, then I can see the appeal of keeping everything in the same configs.

[–] lckdscl@whiskers.bim.boats 1 points 1 year ago

I like to keep the configs separate and not clutter up my compose files.

You can do that with Traefik, I have all my reverse proxy config in a file that hot reloads by Traefik dynamically, so I don't even have to restart Traefik, or even the compose files (that's the problem with Traefik labels), just run compose, add service to said dynamic file, save, and the website is now reachable on the browser.