Took me way too long to figure out, but if you want to use a different name for your docker-compose.yaml file (ie, gitea.yaml) and still have renovate bot look into it and work you need to do the following in your renovate.json file:

{
    "$schema": "https://docs.renovatebot.com/renovate-schema.json",
    "extends": ["config:recommended"],
    "docker-compose": {
      "fileMatch": ["^path\\/to\\/dockercomposefiles\\/.*.yaml$"],
      "enabled": true
    }
}

Of course, adjust accordingly the path/to/dockercomposefiles/ bit to be a regex match from the root of your repository, and add in whatever other renovate config you have.

In my case, this allows me to store all my portainer configs and still have them looked at by renovate without having to stick them all in an ugly folder structure.

If you're wondering what the heck I'm talking about, take a look here. It's basically an automated bot to open PRs/branches (and merge them automatically if you want after checks are passed) on your git repos when stuff updates. Great when you have a few dozen projects.

Bootstrap is really a game changer for a backend dev like myself. I was able to do a loooooot of style changes to implement a nice darkmode theme without too much of a hassle. Ie, the little tweaks I did worked awesome for both desktop and phones!

I also went ahead and adjusted a few other of my front-facing sites. I know I played with it years ago when I last worked on my portfolio site's design, but since then it's gotten even easier. Dark mode gradiants are making my eyes very happy.

Fixed the responsive design! Turns out the code blocks were the issue. Seems to have fixed the gradiant issue as well in the background.

EDIT: Scratch the gradiant issue - still a problem. Do deal with another time I suppose.

Well, I've written enough of this for the evening. I'll seriously need to refactor things for maintainability but at least I got something out there.

There are also at this time some slight usability gripes. Ie, the background gradiant doesn't work right as you scroll down, and I do not have multiple pages to click through ready yet.

This will come in time, but for tossing together a quick blogging platform run via Nodejs and git I'm fairly happy for a couple hours of work, considering Nodejs is not my primary language and I also had to write a whole pipeline + write up the IaC to deploy it in this same time.

Ignore my grammatical and spelling errors as I go along with this - they're just my rambling thoughts to get them out while I work on things, which is basically the point of this blog.

Interesting little find while working on this blog (that is, the software that runs it to be specific): docker does not preserve the file modification times when copying data over.

So since I wrote each of these posts as markdown files and use the modification time as the date of the post, I had to get creative.

Inside my dockerfile instead of a COPY . .

COPY app.tar.gz .
RUN tar -xzf app.tar.gz && rm app.tar.gz

Then I had to add this into my github workflow

- name: Create tarball to preserve file modification times
    run: tar -czf app.tar.gz *.js dir1 dir2

This still didn't work, so I had to look further. So next thing I tried was adjusting the fetch depth of my checkout action to hopefully preserve the file modification times.

- uses: actions/checkout@v4
    with:
    fetch-depth: 0

And this still does not work. So, I had to backtrack a bit and instead switch to using a line of the markdown to define the time. This so far is working fine, but I'm not sure if I like it. I'll have to see how it goes. Timezones are my current concern since I'll be manually typing them in so it's a little clunky, but at least it's a start.