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
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?