this post was submitted on 04 Oct 2026
62 points (98.4% liked)

Selfhosted

63012 readers
1865 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

My blog is currently running on Ghost 1.0 I'm blogging for almost 20 years, started with blogger.com I think, eventually migrated to self-hosted Ghost when it was pretty new and lightweight. I can host anything that runs on Linux, I can even use Docker.

I don't want to migrate to the latest Ghost version because it feels very enterprisey now, needs a lot of resources on the server and uses a complex data format instead of Markdown. I don't need monetization either.

My requirements are:

  • possible to migrate ~30-40 Markdown posts + embedded images from Ghost 1.0
  • future proof, i.e. simple data format so I don't get locked in
  • low RAM/CPU usage
  • easy maintenance, creating posts, backups, etc
  • RSS support

I'll be very grateful for any suggestions.

you are viewing a single comment's thread
view the rest of the comments
[–] notabot@piefed.social 10 points 1 week ago (6 children)

Depending on exactly what features you actually need in term of things like commenting, you might want to look into a static site generator. Something like hugo woud probably do what you need in terms of translating the markdown into a blog. It has the advantage that you can them host the pages on a normal web server, rather than running a blogging platform, giving you a much lighter weight server footprint, and a much smaller attack surface too.

[–] simon574@feddit.org 4 points 1 week ago (5 children)

I don't really need comments, only RSS. Hugo is a great piece of software, I actually use it for my personal webpage. It would be an option for the blog too, my only gripe is that it adds some friction. For example if I want to embed images, I have to upload them somewhere, and manually insert the filename. I also need regenerate the site if I add new posts. I know this can be automated using scripts.

With Ghost it's very simple, I can just write a post, upload the images, hit "Publish" and done. There was even a mobile app for writing new posts, but it doesn't work anymore.

[–] notabot@piefed.social 7 points 1 week ago (2 children)

Hugo can handle images through its asset pipelines, so you should be able to just store them with your markdown. I agree it's a little more friction than a blogging pkatform, but it does mean that you can just write your posts in your editor of choice and publish them with just a command, or if you're feeling fancy, set up git to trigger publishing when you push.

[–] simon574@feddit.org 2 points 1 week ago

This is a good point actually. As others have mentioned, editors like VS Code make working with images in markdown easier. I'm also looking into Obsidian, which I already use on my phone, but it might be too much effort to setup for this purpose.

So I'm warming up to the idea of using a static site generator, just need to figure out a workflow. There is also Zola which is kind of like Hugo but smaller and written in Rust.

load more comments (1 replies)
load more comments (3 replies)
load more comments (3 replies)