These are current graphs for lemmy.world (yet to add it to my Zabbix)
Diskspace:
du -sm *
960 pictrs
1273 postgres
These are current graphs for lemmy.world (yet to add it to my Zabbix)
Diskspace:
du -sm *
960 pictrs
1273 postgres
I see you're using Hetzner. Those graphs don't really show what kind of CPU you're using. It's a 2 core i guess?
I think it depends heavily on how much storage you're allocating, if you allow uploading media that is. From what I've understood most of the bottlenecks are in DB operations so CPU and memory definately play a role.
Good point. I forgot about media.
I wonder if I made a LAN lemmy instance if I could use it as a lemmy cache server.
At least 2.8k :-)
What is the plan to make communities between instances easily accessible? I feel like with mastodon and now lemmy that is the part that concerns me, namely community reach/discoverability
External communities are just searchable, subscribable and browsable from here. Sometimes you need to change a search filter or default view from Local to All. Or is there something else you feel is missing? I think 90% of the issues people are having are UX related and not a core issue with federation or decentralization.
I think my concern for adoptability is that a technology community could exist with the same name on lemmy.world as well as on another instance. I think theirs some benefit to creating a user and community pool of names and communities to allow genuine growth. it would also prevent fakes and phishing.
I think of it like selfhosted@lemmy.world instead of just selfhosted. Sure there may be duplicate communities on different instances but over time I think there will be more people gravitating to a particular community and people will just sub there from then on and the others will become more dormant. When I refer to a community I'll just use the full name (selfhosted@lemmy.world) and not just the community name (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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!