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!
view the rest of the comments
Assuming docker and docker compose are installed on a Linux machine and you have some kind of front end proxy with a valid cert available, just create a folder you have write access to and unzip the file from here: https://cloud.socdojo.com/s/yrATyMZtNTFiLjY
There should be 3 files in it, docker-compose.yml, lemmy.hjson, and nginx.conf
Notable areas to update:
Line 55 of docker-compose.yml is where any attachments of posts get stored, in the case of my files /mnt/NAS/Lemmy where they get offloaded to a remote NAS, change as needed, but the folder should be set with a 'sudo chown 991:991 /mnt/Lemmy' to allow pictrs to write to it. This folder should be created first and the permissions changed before bringing things up.
Lines 20 of nginx.conf and line 17 of lemmy.hjson should match as your domain name, I don't know if the nginx name actually matters honestly but it works for me.
Lines 44 of docker-compose.yml and line 38 of lemmy.hjson should match for your database password
Line 9 of docker-compose.yml the first number is whatever you want your inbound proxy port to be, in the config it's set to 1234
Lines 20 of the docker-compose.yml and line 12 of nginix conf should have the same port number, set as 1234 in these files.
Any other fields tagged as 'ChangeMe' are pretty self explanatory and don't have to match anywhere else, Just updated them to be what you need for email, admin account info, domain hostname, a site title, etc.
After that it should all work, just point your front end proxy at the port you set in the docker compose and away it goes.
docker compose up -d