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:
- 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
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 ...