I did something similar a (very) long time ago (15 years back!), a static site generator and blog engine entirely coded in sh (yes, not even Bash) + coreutils. The idea was to use those scripts in git hooks, as they provide a template engine that allows to use the Git repository as a storage backend and publishing method, both for posts content (as file or as commit bodies) and for meta data about posts (author, date, etc). It was fun to build and got a few dozen users at the time, some even contributed small bugfixes and features :).
I use tree almost every single day and I never realized this. Thank you so much for this wonderful factoid, which has simplified my life immensely, seriously. Going to also adopt a mental note “rtfm||gtfo, ffs.”
Love it! My personal sites tend to start hand-written, evolve into a bash script, occasionally advance into python, but mostly just stay in bash, because it's convenient, doesn't need to please anyone else (nor would it!), and is already built for text processing into files. (I write a lot of scrappy shell scripts for my job too. I guess I should start asking an AI to generate whatever I want directly instead. Cobbling together a script is more fun though...)
It's job is to help me make my website. Thus, its scope, (mis)feature set, polish will always be production-grade, where production is "works on my machine(s)" :)
I'm back! I was nerd-sniped. I made a little ssg for the apps I've created over the last year or two. Being able to generate themed, consistent pages for all my apps is just a huge win. I used node for no real reason other than I've been writing a game in JavaScript recently.
> Also makes me want to make my own little ssg in whatever way I see fit.
Go for it, it's fun! I made one in TypeScript recently as a way to improve my skills there. Be warned though, completing one SSG may lead to wanting to start another haha.
I wonder what would be a good way to generate a website with minimal software installations, for example in standard github runner image. This example uses comrak tool to process markdown into HTML.
I've come up with using Java and XSLT. Java is installed in Github Runner image and there's built-in XSLT support in Java standard library. You can write HTML and use XSLT to add header, footer and do other processings if necessary.
So basically I want to generate a website in github runner without accessing network to install something else.
I guess one could just `cat header.html content.html footer.html` but that requires a lot of tiny things like extracting title from content and inserting it into header, etc. Nothing that lots of greps and seds couldn't handle, of course...
For minimal stuff, I just have a pre-commit hook that runs
pandoc -s README.md -o index.html
I've done the xlst thing as well, but to generate markdown instead of HTML from Zotero export XML as the input. https://github.com/captn3m0/boardgame-research. But again, I throw the make command into a pre-commit because I want the README to be updated in the same commit.
npm pack builds the file locally, then we expose it to the container filesystem where we do a build and check the outputs. You can move dependencies to bundledDependencies in npm to embed them in the image.
However, this is assuming you're rebuilding the static site generator itself every time. If you just want to build a site using an existing static site generator, it's much easier provided that the site generator itself is easy to use (for example, ours has a one-liner to take you all the way from nothing to a local static site running on localhost, see https://statue.dev)
If you aren't changing the SSG code itself between container runs you'd just mount the markdown to the container and pre-install the ssg in the Dockerfile itself. For statue.dev that would just be a Dockerfile almost exactly the same as the one we use already, except you'd use your own script, and RUN this in the Dockerfile itself: yes | npx sv create . --template minimal --types ts --no-add-ons --install npm && npm install statue-ssg && npx statue init && npm install
In your script you'd just npm run build then do whatever it is you want to do to send the files somewhere, and wherever starts the script, you'd do something like -v "pathtomymarkdown/foo:/test-package/" - not sure how to do this in github runners.
Depending on how interested you/other people are in doing this with statue.dev, we could prob get something like this (where the markdown is parameterized, not the npm package) working by Tuesday. We're building out the sandbox/build features on our cloud platform as we speak, this could be one of the first use cases/defaults.
In fact, that is my line of thinking, except "using whatever already exists on my computer(s)", which is: bash, sed, grep, jq, awk, pandoc, inotifywait, and xdotool.
The point being exactly to avoid whatever a third party may or may not deign to let me use, without hassle.
Not quite shell -- but obligatory: I've been using http://zim-wiki.org for now .. decades? As my main driver for most everything in my life, including my personal and teaching website, custom template I made.
Readit News
The README is here: https://p4bl0.net/shebang/fugitive-readme.html
[0]: https://github.com/tasuki/vitwiki/blob/master/build.sh [1]: https://wiki.tasuki.org/
I do somewhat wonder why not pandoc, but it is still an interesting project
I remember setting up a few of these back in the day.
https://nanoblogger.sourceforge.net/
It's job is to help me make my website. Thus, its scope, (mis)feature set, polish will always be production-grade, where production is "works on my machine(s)" :)
Go for it, it's fun! I made one in TypeScript recently as a way to improve my skills there. Be warned though, completing one SSG may lead to wanting to start another haha.
I've come up with using Java and XSLT. Java is installed in Github Runner image and there's built-in XSLT support in Java standard library. You can write HTML and use XSLT to add header, footer and do other processings if necessary.
So basically I want to generate a website in github runner without accessing network to install something else.
I guess one could just `cat header.html content.html footer.html` but that requires a lot of tiny things like extracting title from content and inserting it into header, etc. Nothing that lots of greps and seds couldn't handle, of course...
npm pack builds the file locally, then we expose it to the container filesystem where we do a build and check the outputs. You can move dependencies to bundledDependencies in npm to embed them in the image.
However, this is assuming you're rebuilding the static site generator itself every time. If you just want to build a site using an existing static site generator, it's much easier provided that the site generator itself is easy to use (for example, ours has a one-liner to take you all the way from nothing to a local static site running on localhost, see https://statue.dev)
If you aren't changing the SSG code itself between container runs you'd just mount the markdown to the container and pre-install the ssg in the Dockerfile itself. For statue.dev that would just be a Dockerfile almost exactly the same as the one we use already, except you'd use your own script, and RUN this in the Dockerfile itself: yes | npx sv create . --template minimal --types ts --no-add-ons --install npm && npm install statue-ssg && npx statue init && npm install
In your script you'd just npm run build then do whatever it is you want to do to send the files somewhere, and wherever starts the script, you'd do something like -v "pathtomymarkdown/foo:/test-package/" - not sure how to do this in github runners.
Depending on how interested you/other people are in doing this with statue.dev, we could prob get something like this (where the markdown is parameterized, not the npm package) working by Tuesday. We're building out the sandbox/build features on our cloud platform as we speak, this could be one of the first use cases/defaults.
The point being exactly to avoid whatever a third party may or may not deign to let me use, without hassle.
jrm4.com