When I originally started writing this blog, The process for actually getting it online meant manually running the process to generate the pages, and then uploading it to my server. This process was functional but a real drag on my time, meaning that I never felt like writing a blog article due to the length of the process.
The first part of making a better solution was realising I had the tools to do this in hand already. My blog is a git repo, and is hosted on my gitea server, and a long while back as part of making it easier to build and test programs that I have written, I configured actions 1
It took me a while to get things working the way I planned, while there is plenty of documentation on the general writing of actions (both original GitHub Actions, and Gitea Actions) it’s mostly up to the end user to actually synthesize that information into a coherent workflow.
After many attempts and dead ends I can finally do the following steps:
pandoc - used by my code to generate the pageswget - grab some files (used by another step)rsync - to push the blog changesopenssh-client to rsync securelytree for debug purposes (TODO: remove)cssitegen
projectcssitegen verbosity optionsAs you might tell from the distance in time from each article. I don’t write many. But this is more that I didn’t want to keep putting in the effort it took to then publish them.
This takes all the hassle out of it, since to publish anything now,
all I need to do now is push main and the action does the
rest.
Hopefully this will bring about a wealth of new articles as I have some cooking away in my head.