this post was submitted on 29 Jul 2023
517 points (95.8% liked)

Selfhosted

40042 readers
861 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

First post from my new, self-hosted, personal instance. Feels good!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 17 points 1 year ago (4 children)

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.

[–] [email protected] 7 points 1 year ago (1 children)
[–] [email protected] 5 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

From the readme:

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.

[–] [email protected] 2 points 1 year ago

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

[–] [email protected] 5 points 1 year ago (1 children)

Do you know how much disk space this will roughly use? Are we talking 10GB or 100GB or 1TB? Just roughly speaking.

[–] [email protected] 2 points 1 year ago (1 children)

Mine went from 8 gb to 20-ish gb. So not that much ;)

[–] [email protected] 1 points 1 year ago

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

[–] [email protected] 2 points 1 year ago

Thank you for the info. I set my instance up yesterday as well and my goal today was to do this.

[–] [email protected] 1 points 1 year ago (1 children)

Just so you know, this also creates more load on other instances, especially the larger ones.

[–] [email protected] 1 points 1 year ago

Hmmm that is not really the small instances “fault”, but that is the idea of the Fediverse…