Routhinator, (edited )
@Routhinator@startrek.website avatar

If you are looking for true low maintenance, avoid needing a DB. So I’d stay away from the WordPress suggestions. Not to mention keeping WordPress CVE free is often a full time job and the opposite of low maintenance.

I’d use one of the many tools out there that takes Markdown and coverts it to HTML, stick that in a basic CI job on Gitlab or Github to build out my HTML and I just write markdown.

Once that’s in place how I would decide if I wanted a custom domain.

If I don’t need a custom domain, then I can just augment the pipeline to publish to Gitlab/Github pages.

If I want a custom domain then it depends on budget and expected traffic, but I’d likely just put it on an ECS container or in an S3 bucket and shove cloudfront in front of it, because if it’s small enough it will likely qualify for free tier AWS. If it’s too big for free tier then I’d stick with a container but likely either put it on a cheap cloud node with Apache and letsencrypt and one of the smaller providers like Linode/DO/Vultr

  • All
  • Subscribed
  • Moderated
  • Favorites
  • asklemmy@lemmy.world
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #