“Why did I do this” #
Contrary to appearances, I don’t spend a lot of my time writing for this blog. So naturally, when I do think of something, it’s been long enough that I’ve completely forgotten how I set it up. So let this post be a self-documenting one on how I’m running this.
The Platform #
Gitlab, when they’re not nuking their prod database, is at least not owned by a company that wants to take screenshots of your computer every five seconds to be processed by their (TOTALLY TRUSTWORTHY, TRUST US, GUYS!) AI bots. So, that’s where this little blog lives.
As you can see on there, I’m using Hugo to generate static pages that are ultimately hosted on Gitlab as well. (Gitlab’s CI supports running the hugo tool on their end to generate those files.)
(As a brief aside, on my end all these files used to be stored in Nextcloud, but I got fed up with it and moved to Seafile. Maybe I’ll map out my home lab setup some day.)
All told it’s pretty nifty–I just often forget where to jump in to actually create new content. But as luck would have it, it’s the “content” folder in the Hugo folder structure that contains that content.
So in the end it’s pretty simple, once all the backend wiring is hooked up on the Gitlab/CI side: add a new .md file to that folder, make sure it’s not flagged as a draft, git commit and git push, and wait for the ad revenue to roll in.
Swimming in a pool of ad money Scrooge McDuck style,
- Tyler
