dustin/dustin.web/pipeline/head This commit looks goodDetails
The problem with having stages that only run in some situations is that
they don't get tested.
Need to mount the SSH host key database file in the _rsync_ container so
the host key of the web server can be verified when publishing.
Sometimes, I want to see what the built site looks like before
publishing it. For that, I'll push changes to a dev branch and let
Jenkins build the site as a tarball that I can download, extract, and
view locally. Once I am satisfied, I'll merge the dev branch to master,
which Jenkins will build and publish to the live site.
* The _zola_ container image no longer contains Python, but it does
contain `pause`.
* When using `python` as the entry point, we need to explicitly register
a signal handler for SIGTERM, otherwise `signal.pause()` will never
return.
* The _rsync_ container image now has a default pause entry point.
Possibly the main reason I haven't published the _Projects_ section of
my website, despite having worked on it for several years, is I never
felt good about how the cards on the index page looked. I think this
new style looks _much_ better, to the point where I'm thinking about
publishing it finally!
Using the "combining long solidus overlay" Unicode character to draw the
"slashed zero" does not look very good on many systems. It looks fine
on my local machine, with the DejaVu font package that comes with
Fedora, but that's about it. The web font apparently does not have this
character, so browsers fall back to another system font to render it,
which can have varying results.
The DejaVu Sans Mono font has a "dotted" zero, which is similar enough
to a "slashed" zero. Unless you're looking very closely, you can't
really see that the callsign is in a different font, so I think this
works fine.
I really don't want to use the "Latin capital O with slash" character
for this, since that is completely incorrect, but I do want to have the
zero stylized like ham radio operators do.
I don't like relying on GitHub to serve *normalize.css* for two reasons:
1. It sends a tracking cookie
2. I don't trust that the stylesheet will not change arbitrarily and
negatively impact my site
I'm probably never going to write blog posts frequently enough to
warrant having the main focus of this site be the recent posts.
Instead, the home page can just be links to each section of the site.
The icons used here are from the [Material Design Icons][0] project.
[0]: https://materialdesignicons.com/
Since we're pre-rendering the page now, we can't select a song quote on
the server side. Instead, we'll use JavaScript to fetch the song quotes
as a JSON document and choose a random song from there. The JSON
document is converted from the YAML source at build time with a simple
Python script.