• 0 Posts
  • 17 Comments
Joined 7 months ago
cake
Cake day: March 30th, 2026

help-circle



  • I love ghost’s UI and feature set.

    What complex data format are you taking about? Last time I checked, it was plain markdown in a database (even supporting sqlite).

    What I’d recommend though, is coupling it with a static site generator and only using the ghost server for the administration / authoring (guides). That way, serving the blog to visitors is basically free in terms of resources (at last as low as it gets). You could even push these static builds to a CDN (yes yes, selfhost community, I’m just saying it for completeness)

    It might be some hassle to set this up somehow, but you could even have the container stopped unless you actively need it. You could even run the server application on your computer instead of the server, unless you want to access is from a smartphone/tablet.


    If you really want an alternative to Ghost and don’t need user management and an online WYSIWYG editor, you could go straight to an SSG and feed itraw it markdown files.












  • I haven’t tried any out-of-the-box solution or setup script, so I can’t talk about them. if you go diy or want to edit any solution to have internet access exclusively over VPN (or not at all otherwise), I can recommend gluetun. Other than that, I just have a simple docker compose file and a reverse proxy. I recommend not exposing it to the www, but to keep it only accessible in your local network, or tailscale, if your use case allows it. Note: if you set up https, you might be leaking your subdomains in permanent certificate transparency records.



  • At work I use kubernetes and quite like that (upgrading containers without downtime FTE), but I didn’t bother trying to set up the infrastructure myself. Some argue, it’s not with the efford for self hosting, I dunno.

    What I do like to use is Dockge, to keep docker but also keep your sanity. It even offers a single button for “docker compose pull”, which is great of you don’t have to many compose files / stacks. Combine with a simple shell script to batch pull/build all stacks in one go, plus some backup solution, and it’s actually nice to use and does all that I need. I love CLIs, but I’ve had situations where the GUI came in very handy.

    #! /bin/bash
    # note: this will update and START all dockge stacks, even if you stopped them before
    shopt -s nullglob
    for proj in /opt/dockge /opt/stacks/*/; do
      echo "> $proj"
      docker compose -f "$proj/compose.yaml" up --pull always --build --detach
      echo ""
    done