I started learning github actions (and wrote about it). Not true. I was reading about them, trying to understand how they work. I invested one day, after clarifying the terms for me I figured out that I can go as simple as using some actions from the github marketplace and be done. But I prefer to understand what's under the hood. So I did dive in and found that there are multiple repos and more, there is a power behind github actions that seems to go beyond what travis, drone or jenkins offer.
Which unit to use,
em or even
px (just to mention the most common units) when writing CSS
seems to be an ongoing discussion. For people entering the space of web development
the hurdle just gets higher, the complexity is continuously growing. There are
more units than ever, I counted 21,
there is more sites to learn from. It is not easy to figure out where and how to start.
I will try to analyze this a bit applying what I know and have learnt over the last 25 years of web development.
I just watched the very good, How to run Nginx inside Docker container
video. In 9 minutes you will learn the basics of docker while starting up an nginx server running on docker.
The real take away for me is the updated docker commands, which are finally as explicit as I always had wished
they had been from the beginning. Like
docker container run which was
"Failed to construct 'CustomElement': The result must not have children"
The title does not really enclose all the topics and cover the full value of this talk. Actually it is not explicit enough, because sustainability is a word that is being used in too many contexts and means too much. I would maybe rephrase the title to "The Real Cost and Value of Open Source and Why and How Your Company can Participate and Give Back". A bit clunky, but it tells the story I believe.
I just came across an article again, that had "(sic!)" in it, and I finally looked up what it means. I also see it in german text. So it's time to look it up and learn what it means and how to use it when appropriate.
While reading about github actions I note down a couple of things here, that I find worth noting and remembering. Basically I can imagine what it looks like, it's a travis with a tighter integration into github, but some details are interesting.
Lately I thought more often about automating my blog using webmentions and while reading the Github Actions docs, I found the following might come in handy. So I am parking that info here.
I wanted to deploy to github-pages using the renamed branch "main", but it seems not to be possible with github (yet) to turn on github-pages with a branch different then "master". So I thought it might be a good time to try out github actions, maybe this will help? If not I will have learned something.
Michael Feathers wrote Functional Code is Honest Code. I will take away questions from this article.
It is painful sometimes, but having a setup that works on any machine (that has docker), just git-clone and run is AMAZING. I use a bash script and a 2-line Dockerfile for it.
provides a CBE (Customized Built-in Element) for upgrading heading tags such as H1, H2, ...
to render a link-icon beside them, as many know it from github readme files.
I wanted to upgrade all picostitch sites automatically by just including a
which upgrades all headings on the page and adds this functionality.
It is not possible to upgrade a parsed and rendered element (like an H1) afterwards.
I saw a video that VS Code creates directories and file when
adding a file named like
dir1/dir2/file.js, I tried it in WebStorm.