Lately I've been busy giving all the tools I am using a new coat of paint (Or just pulling the newest stable image). I've replaced the old Nginx Proxy Manager with Traefik as the proxy manager had a tendency (for me at least) to corrupt its data. Now the domains are managed by the labels on their respective docker containers. I've moved most of my domains to CloudFlare (except for Neigh Dev) and I've updated the rest of the software.

Because I'm hosting quite a few services I thought it'd be fun to use the Trilium export job I made for Neigh Dev to generate a new site just for me. Though, I don't really expect this site to have any visitors(, except for me of course).

I mentioned in 2023-12-20 Break it yourself that software tends to break by itself. Another weird aspect is that when you build software to solve a problem (or create a problem you want to solve with software), it doesn't automatically solve the same problem in a slightly different location.

In this case to make it work for an additional site the following things need to be fixed:

  • The root note needs to be configured from within Jenkins 
  • It must be possible to select a different target than Github 
    • I'd prefer to keep those pages private because they aren't useful to anyone but me.
  • There is a lot of overlap between the Python script and the Jenkins script, they need better separation.

A feature on my wish-list would be to automatically trigger updates to the site, up until now I've always checked the results of an export before giving it my blessing. But there are now enough safeguards in place that I feel comfortable enough letting it decide on its own that it is go-time.