If you do this, you will need some extra space because the database will grow, but I think it solves one of the (largest) downsides of running your own instance, namely discovering other communities.
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.
As of the writing of this tool, and size of the fediverse (Jul 2023), using this tool, may result in disk space usage of around 2GiB/day, according to my own metrics.
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…
The latest really improves things space wise and cleans up better. Single instance here for almost a month. About 50-60 subscription’s and am at 2gb db size
Welcome to the club! I used the same easy deploy setup as you! Makes life really easy eh :)
Furthermore, to populate All, I have this one running: https://github.com/lflare/lemmy-subscriber-bot
If you do this, you will need some extra space because the database will grow, but I think it solves one of the (largest) downsides of running your own instance, namely discovering other communities.
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…
Do you know how much disk space this will roughly use? Are we talking 10GB or 100GB or 1TB? Just roughly speaking.
Mine went from 8 gb to 20-ish gb. So not that much ;)
The latest really improves things space wise and cleans up better. Single instance here for almost a month. About 50-60 subscription’s and am at 2gb db size
Thank you for the info. I set my instance up yesterday as well and my goal today was to do this.
Just so you know, this also creates more load on other instances, especially the larger ones.
deleted by creator