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
Personally... it was an experience to say the least. I went down the Docker path for my instance. I've tried to keep away from Docker for ages, but here I am.
I'd recommend using the ansible playbook to get it running, as the docker documentation isn't very detailed and it gets very confusing; especially for a beginner.
The docker documentation is not kept in sync with the docker-compose.yml it asks you to use. So you download the latest one as per instructions, but that's being regularly updated with no thought to the documentation also being updated. It's also doesn't seem aimed at production deployment, just developer test environments. Then there are stupid simple things like the port number being changed in the docker-compose.yml but not in the nginx.conf or the lemmy.hjson. There desperately needs to be better control of that.
There is a lot wrong there and it doesn't fill me with confidence. It took me 3 hours to piece it all together last night and had to revert to picking bits out of the ansible documentation.
Exactly, I’ve spent ages yesterday and today trying to piece together a set of configs that all work together. I thought it must have been me missing something because the last time I did it everything worked exactly as described in the documentation and it took about ten minutes to get a working instance up and running, but not this time!
It helps slightly (slightly!) if you refer to the configs from the last release rather than the ones on the main branch that are constantly being changed, but even then you’ll have to maybe use the docker-compose.yml from the Ansible repo if you don’t want to build nginx as part of the docker install.
Got there in the end though!
Turns out I can't upload photos due to the config file they point you at being wrong. Ffs! Direct users to a labelled release and production version. At the moment it's chaos at the very time it needs to be as seemless as possible.
+1 for Docker, specifically Docker Compose. Lemmy probably isn't the right container to learn Docker with, but once you have the fundamentals down spinning up Lemmy was pretty seamless.
thanks, wanted to go that route
Make sure you use a Debian base OS, as the playbook uses aptitude to install the dependencies. Also, you can't use anything over Debian 11, as the way the apt repositories and gpg keys are added, and the pip packages are installed don't work with the newer OS'.
I found out the hard way lol
Did you start with arch or something 😂 sounds like you went through it lol
Not even ha, just tried to install on Debian 12