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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Lemmy, although in a very well working state, isnt really deploy ready. The update procedure is a mess, the documentation is less than stellar and accessibility/onboarding for wannabe admins is rough to say the least.
You can find a compose file on github and you will need to make a config file for the instance with your domain and all on it.
A one click install sure is doable but most people who are able to do this quickly are very busy or wont do it for free.
I ended up going down the Ansible route after spending about 6 hours trying the easy-deploy and "manual docker install", failing miserably with both.
I expected the other methods to be easier but nothing ended up working. Tried the official ansible method with a caddy proxy and it took maybe 30 mins.
I would definitely have given up if I wasn't so stubborn.
Great! Glad it worked out for you. The second time I deployed lemmy on a production machine it was markedly easier because I have a known working compose and lemmy.hjson file so thats one part. I think the first install/config took me days of tinkering.
At the moment, I cant see if I‘ll havre the time to ever make a cone click install script but I‘ll think about it.
Good luck with your instance.
https://github.com/ubergeek77/Lemmy-Easy-Deploy used to work well, not sure if it is maintained still @ubergeek77@lemmy.ubergeek77.chat ?
It should still work!
I only go back and make changes to LED if something breaks with a major Lemmy update, but Lemmy hasn't had a major update since January. Lemmy v0.19.4 isn't released yet, but when it is, I'll make sure the deployment is up to date.
Note that it does not have any advanced features that a major instance might want, such as storing images on S3, exporting data, or image moderation. If you intend for your instance to grow for 100+ users, this isn't for you. This is only intended for beginners who are overwhelmed by the other Lemmy hosting options, and want an easy way to host a small single-user or small-user instance.
Well it works well enough for my small instance, so a thimbs up from here.
I'll also point out that it was easy to configure and chang for my needs
Hey OP, I found this install script for yunohost.
https://github.com/YunoHost-Apps/lemmy_ynh
Maybe that's enough to help you create the same for C Panel or something like it?
I hear you. I just yesterday tried the docker apporach and gave up after the fourth error occurred during startup. I'll watch this thread and hope for a simpler solutionfor a mere mortal to follow. (Edited)
The docker instructions are a hot pile of garbage, unfortunately. The referenced docker compose file, for example, is for installing via Ansible I think. There's another Docker Compose file somewhere in the GitHub which is formatted for regular installation.
FYI here's a link to the other compose file I was talking about: https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
Lemmy is little too complex for a one click install.
Lemmy consists of:
Each one of those has a number of environmental config options that need to be set before running it all. You need a domain name so that other instances can reach your instance. Your database needs a password, Pict-rs needs to know where to store things, etc.
With docker-compose it's almost there. Putting everything into a script with sensible defaults asking just for what is absolutely necessary should be relatively easy. It's just that nobody bothered to do that.
Of course, if you want to have a performant instance with more than one user you will have to tweak everything according to your needs. But to simply get up and running isn't that hard.
I put you back to +1.
What if I want to run lemmy entirely within my lean only?
So I don't have a domain name. Does that make the setup any easier?
It's absurdly complex and annoying and lacks proper documentation.
There currently is no sane way to deploy it via docker since it needs half a dozen of different containers and volumes and networks to barely work at all - overwriting/ruining your already existing setup while doing so.
The cleanest would likely be setting up a VM where you set up docker in and let Lemmy do whatever it wants.
Mine's running on a single docker-compose.yml and it's like 4 services: the backend, the frontend, the database and pictrs. That's hardly insane nor complicated nor ruining existing setups.
It's probably one of the easiest services I've run in quite a while.
It's also very easy to make it highly available and to scale horizontally.
And two networks and a reverse proxy and four more volumes ...