view the rest of the comments
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.
-
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!
Instead of official lemmy documentation, I recommend https://github.com/ubergeek77/Lemmy-Easy-Deploy
I use it myself and it was too damn easy. Just follow the instructions on the GitHub and you'll be up and running in less than a minute
I've been running around Lemmy trying to get new people to use this. This script is awesome and saved me so much time.
I gave that a try but actually ran into a problem with that too. I setup Mastodon on the same server earlier and was planning to use Nginx server blocks to send traffic for mastodon.fdr8.us and lemmy.fdr8.us to the appropriate destination, but the script failed when it tried to bind all traffic on port 443 and Mastodon is already listening on port 443. I had hoped for both to listen on port 443. This is actually somewhat unfamiliar territory for me as usually I am working with Apache and virtual hosts, but I'm hopeful I can make it work. I am very familiar with Apache virtual hosts and have worked with them extensively. I hope I wasn't crazy to assume I could run Lemmy and Mastodon on the same server on Nginx in a similar fashion.
Thanks for the advice. I'm old school and never use Docker, but maybe it's time I get over that. I'm actually out of my element anyway in that I do a lot of self-hosting but up to this point it has almost all used Apache and MySQL rather than Nginx and Postgres. Hopefully someone will come along with a solution for the diesel-async compiling error while I'm at work for the next few hours, but if not I'll give your suggestion a shot this evening.
You'll have to do some reading, but here's some (almost) turnkey repos for all the pieces you need to host Lemmy (and other things) in docker.
I use Traefik instead of nginx to do load balancing / edge routing / reverse proxy / SSL termination (and automatic generation via LetsEncrypt - it's proven to be bulletproof in a good few production setups.
Oh wow that's amazing! Docker really is amazing for hosting stuff nowadays though!