12
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Jul 2023
12 points (87.5% liked)
Selfhosted
39677 readers
368 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
Think of the NGINX proxy in Lemmy's
docker-compose.ymlfile as the entry point to Lemmy from outside the Docker network. For instance, I don't have any ports mapped for the individual services except for the NGINX service. The NGINX proxy in this docker-compose file will access the other services through the internal docker network, so it isn't a problem if you set up yournginx.conffile with the service's names. With that done, you could map any port you want for the NGINX service from the host, then point your internet-facing reverse proxy to that.I also plan on setting up a Mastodon server, but I haven't gotten to it yet. So I don't have anything specific to add other than it will work similarly by using docker's port mapping or service names depending on whether each service needs to be internet-facing or only communicate internally.
In the configuration of the docker proxxy, do I define my domain name (like lemmy.my-domain.tld) or will I define some local IP (like 172.20.0.1) and let nginx proxy manager point to that?
You can use the FQDN of your Lemmy instance in the
nginx.conffile. I've uploaded my files to a gist here as an example.You should be able just to replace any mention of
lemmy.mydomain.comwith your FQDN of your Lemmy instance and replace anyyour-postgres-passwordwith your real Postgres password. You must also set your SMTP provider settings in theemailsection ofconfig.hjson(I use Brevo). In thedocker-compose.ymlfile, you can change which port you want to map from the host; I used8976in mine. Then just point your internet-facing reverse proxy to the host and whichever port you chose.I'm not using Ansible to automate it at all. I'm just updating the files manually, as needed, and doing
docker composecommands. I'm using Docker volumes to persist the data on them, so feel free to change any of those basic things you want.thanx! I got it running now, not sure yet if federation is working, but at least I have my instance up and could register admin + standard user :)