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
Thank you; bookmarked.
When you decide to set it up, you need to create a user on your instance and fill in those details in the command line to run the thing. Also make sure to change the instance name to your name, otherwise it will not work.
Other useful commands:
docker rm --force lemmy-subscriber-bot To actually destroy the docker container if you want to start over
docker logs lemmy-subscriber-bot To see if the thing is running and doing things.
From the readme:
Seems kind of steep. I only have 500GB allocated to my server. I feel like there's got to be a better way.
I have the feeling that this is extremely exaggerated. I only have 40 Gb in total and still have 23 gb free. I don't run the tool constantly, but run it every once in a while to make sure that my All has interesting communities. If it would be 2 gb/day I would be loooooong over my 40...