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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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
It wants a gigabyte of RAM. Maybe that passes for lightweight in 2025, but given the fundamental things a blog has to do, I'd probably put the cutoff at less than a tenth that amount.
It costs like $3/mo to host it. If that's too resource intensive then I don't know what your limits are. Compute isn't free—that literally breaks the laws of thermodynamics, no matter what you're told by hosting services, and ghost does server side rendering and has a dynamic admin dashboard and can even work headless... and it costs less than $3/mo for your own personal open source cms.
If you need something that costs less then you can just build your own I guess, but how many hours of your time is that worth when you could just be spending $3/mo. If you make minimum wage at $7/hr one hour of work gets you two months of running a website.
Not if you want federation.
The answer is probably GoToSocial, which suggests that it can run on 512MB.
Federation doesn't inherently require large amounts of memory. Fundamentally, it's a matter of selecting a list of unique servers (likely tens, maybe hundreds) from a larger set of followers (likely hundreds, maybe thousands) and sending an HTTP request to each when there's a new post. There's a speed/size tradeoff for how many to send in parallel, but it's not a resource-intensive operation.
Growth beyond a few tens of megabytes was a bug in Writefreely, which is a likely-suitable option several comments here recommended.