I didn't have to make any changes from 0.17.4 to 0.18.0 beyond updating my docker compose to the new version; tunnel config stayed the same, nginx config was the same, and the docker compose network config was the same.
this post was submitted on 27 Jun 2023
2 points (100.0% liked)
Self Hosted - Self-hosting your services.
14519 readers
54 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 4 years ago
MODERATORS
Could you post your tunnel config? Or an simple one. Ive got a bunch of services on it but its straightforward what ip and port i have to point to. With federation in the mix i dont know the aetup in cloudflare should be. Does it point to nginx? Lemmy app, lemmy ui? Thats my missing knowledge
I'm configured to point the cloudflare tunnel -> nginx container in the lemmy stack -> nginx.config provided by the devs reverse proxies the rest of it.
Thanks