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.
I'm thinking like a programmer about what a basic blog has to do and the computing resources necessary to accomplish it. Software that needs more than a few tens of megabytes to accomplish that is not lightweight regardless of its merits.
This comment seems to be arguing that one should not demand blog software be lightweight because there's inexpensive hosting for something heavyweight. That's a fine position to take, I guess, but OP did ask for lightweight options.
Im merely making a value proposition because im an engineer and I've had this same exact problem and desire. Call it experience — a static blog is fine since I can build one of those in my sleep, but for me I wanted to post on it when I was away and only had my phone. Now do I put it on my git? A separate notebook that is synced somewhere? I have ADHD—if I want to write I have to write and I can't just hope to remember it sometime later. Now what's the point of my blog if I can't write on it when I need to but simply don't have my desktop nearby? Also you have to have pay for a CI to do the building anyway for a static site generator, that ain't free and even if you found a service that provides CI for free you're just externalizing your costs somewhere else. Laws of thermodynamics still apply. So instead of paying for CI to build your static site, I'd argue just pay for the server rendered site. Why choose to have a 1gb ram build server for a blog when you can just use that server to run the blog.
And they want federation support. Ghost is working on that as well speak. What static site generator supports federation?