Selfhosted

61030 readers

732 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Why is everyone using Tailscale? Edit: I meant Traefik (lemmy.world)

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

29 comments fedilink hide all child comments

Title. I looked at how to configure anything and found Caddy to be much easier to use. Aside from a lot of docker images integrating with it, why is everyone using it? Edit: I meant Traefik

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

[–] uranibaba@lemmy.world 1 points 1 year ago (1 children)

I meant Traefik, sorry.

Also, why Nginx over Caddy? How does a minimal reverese proxy setup look like with Nginx?

[–] undefined@lemmy.hogru.ch 2 points 1 year ago (1 children)

It’s mostly about performance. Caddy’s Go-based garbage collector starts to negatively impact performance at high load. It looks something like:

server {
    listen 443 ssl http2;
    server_name example.com;

    ssl_certificate     /etc/nginx/ssl/fullchain.pem;
    ssl_certificate_key /etc/nginx/ssl/privkey.pem;

    location / {
        proxy_pass http://localhost:3000/;

        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

[–] uranibaba@lemmy.world 2 points 1 year ago (1 children)

How do you know which headers to set? I couldn't find any documentation when I last tried (but that was some years ago now).

[–] undefined@lemmy.hogru.ch 1 points 1 year ago

It can be specific to the web application but generally speaking you’d want to pass the protocol, client IP address, etc.