<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://arwedus.github.io/</id><title>Thoughts on Programming, Technology and Software</title><subtitle>Notes and solutions on programming, technology and software.</subtitle> <updated>2026-10-16T13:17:32+02:00</updated> <author> <name>Arwed Starke</name> <uri>https://arwedus.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://arwedus.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://arwedus.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Arwed Starke </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Publishing a Jekyll site with a custom GitHub Actions workflow</title><link href="https://arwedus.github.io/posts/publishing-jekyll-on-github-pages/" rel="alternate" type="text/html" title="Publishing a Jekyll site with a custom GitHub Actions workflow" /><published>2026-10-16T00:00:00+02:00</published> <updated>2026-10-16T00:00:00+02:00</updated> <id>https://arwedus.github.io/posts/publishing-jekyll-on-github-pages/</id> <content type="text/html" src="https://arwedus.github.io/posts/publishing-jekyll-on-github-pages/" /> <author> <name>Arwed Starke</name> </author> <category term="docs-as-code" /> <summary>After I migrated my WordPress blog to a Jekyll site, one very important step remained: publishing that site to https://arwedus.github.io/. Creating a Github Pages Site I followed the GitHub documentation on creating a GitHub Pages site with Jekyll to set up the repository. When you create a repository whose name ends with .github.io, GitHub automatically adds a pages-build-deployment workflow...</summary> </entry> <entry><title>From WordPress export to a Jekyll site</title><link href="https://arwedus.github.io/posts/wordpress_export_to_jekyll/" rel="alternate" type="text/html" title="From WordPress export to a Jekyll site" /><published>2026-10-15T00:00:00+02:00</published> <updated>2026-10-15T00:00:00+02:00</updated> <id>https://arwedus.github.io/posts/wordpress_export_to_jekyll/</id> <content type="text/html" src="https://arwedus.github.io/posts/wordpress_export_to_jekyll/" /> <author> <name>Arwed Starke</name> </author> <category term="docs-as-code" /> <summary>In the previous post I converted my WordPress blog into Markdown files. This post covers the second half: turning those files into a working Jekyll site that I can publish on GitHub Pages. Starting point The converter left me with one folder per year. Each post is either a single YYYY-MM-DD-slug.md file, or a YYYY-MM-DD-slug/ folder containing an index.md and an images/ subfolder: 2014/ 20...</summary> </entry> <entry><title>Exporting a WordPress blog to Markdown</title><link href="https://arwedus.github.io/posts/wordpress_export_to_markdown/" rel="alternate" type="text/html" title="Exporting a WordPress blog to Markdown" /><published>2026-08-21T00:00:00+02:00</published> <updated>2026-08-21T00:00:00+02:00</updated> <id>https://arwedus.github.io/posts/wordpress_export_to_markdown/</id> <content type="text/html" src="https://arwedus.github.io/posts/wordpress_export_to_markdown/" /> <author> <name>Arwed Starke</name> </author> <category term="docs-as-code" /> <summary>My workflows are increasingly based on docs-as-code and Markdown. Markdown files are easy to access locally, quick to edit and search, and work well with the tools I use to build a personal knowledge base. For those reasons, I decided to move the content of my WordPress blog to Markdown. The wordpress-export-to-markdown project does exactly that: it converts a WordPress export file into Markdo...</summary> </entry> <entry><title>How to make docker in VS Code devcontainer use the host network</title><link href="https://arwedus.github.io/posts/how-to-make-docker-in-vs-code-devcontainer-use-the-host-network/" rel="alternate" type="text/html" title="How to make docker in VS Code devcontainer use the host network" /><published>2025-02-21T00:00:00+01:00</published> <updated>2025-02-21T00:00:00+01:00</updated> <id>https://arwedus.github.io/posts/how-to-make-docker-in-vs-code-devcontainer-use-the-host-network/</id> <content type="text/html" src="https://arwedus.github.io/posts/how-to-make-docker-in-vs-code-devcontainer-use-the-host-network/" /> <author> <name>Arwed Starke</name> </author> <category term="computers-and-software" /> <category term="linux" /> <category term="docker" /> <summary>If you have a complex set up, e.g. with VPN and proxy, and docker with an isolated (bridge) network is unable to connect to the internet or is even mis-configuring your DNS name resolution on the host machine (I will add another post on that), the docker option --network=host often helps. It tells docker to simply re-use the network connections of the host machine. However, this is not the def...</summary> </entry> <entry><title>How to tar files matching a given name pattern in all subdirectories</title><link href="https://arwedus.github.io/posts/how-to-tar-files-matching-a-given-name-pattern-in-all-subdirectories/" rel="alternate" type="text/html" title="How to tar files matching a given name pattern in all subdirectories" /><published>2024-03-07T00:00:00+01:00</published> <updated>2024-03-07T00:00:00+01:00</updated> <id>https://arwedus.github.io/posts/how-to-tar-files-matching-a-given-name-pattern-in-all-subdirectories/</id> <content type="text/html" src="https://arwedus.github.io/posts/how-to-tar-files-matching-a-given-name-pattern-in-all-subdirectories/" /> <author> <name>Arwed Starke</name> </author> <category term="computers-and-software" /> <category term="linux" /> <summary>This is just a quick repost of https://stackoverflow.com/questions/18731603/how-to-tar-certain-file-types-in-all-subdirectories, because I find it so useful: Given a directory with deeply nested subdirectories, and I want to just extract e.g. all *.yaml configuration files, this is the command to do it: find . -name "*.yaml" | tar -cvf my_archive -T -</summary> </entry> </feed>
