Let’s explore how to add a dev container to our Node.js bot-zero project. We’ll help the end user to understand how to run the project by adding a profile script whenever the terminal is openend in Visual Studio Code.
Read the article A Dev Container for Bot Zero
At Wehkamp we’ve been using ASP.NET for a long time. Containers brought .NET with us to our microservices architecture. We used a shell script in a special build container to build our service. Today we’ll discuss how we turned that shell script into a multi stage build Dockerfile.
Read the article Rethinking our ASP.NET Docker CI
When I build containerized apps that need to be exposed on the internet, I usually need to forward ports, set up let’s encrypt and reverse proxy some random port. In this blog I’ll show you how to ditch all of that in favor of 1 secure Cloudflare tunnel in a docker-compose file.
Read the article Expose docker-compose app with a secure Cloudflare Tunnel (cloudflared)
Let’s run Jupyter notebooks in a Visual Studio Code development container, so we keep our host system clean and our development setup replicable. We’re building a scraper, so let’s add support for Puppeteer (pyppeteer) as well!
Read the article Jupyter Notebooks + VSCode Dev Container with Puppeteer support
I imagine your first thought is: why? Well, at Wehkamp we do a lot of cross platform development, but sometimes we end up with shell scripts that do stuff with Docker and Python. Usually that’s not a problem for Mac, but for Windows it’s a different thing. I have a MacBook Pro, but I’m a .NET developer, that’s why I prefer Windows, so I run Bootcamp. This article will show how to do Python development in the Windows Subsystem for Linux (WSL) using Visual Studio Code and Docker.
Read the article Visual Studio Code + Docker + Python using WSL in Windows on Boot Camp
My Synology disk crashed and so did my Docker set up. Basically, the CI/CD pipeline for my programs no longer existed. The wonderful thing of an awful crash like this, is that I could rethink my setup. The result is what I would call “a poor man’s CI/CD”. It’s just Git, Docker, Docker Compose and Cron. It is easy to set up and it might be all you need.
Read the article Docker on Synology: from git to running container; the easy way
.Net now runs on your Raspberry Pi (awesome!). Tired of xcopying the result to your pi? In this article I’ll explore how to build a CI/CD Bitbucket pipeline that will build and deploy the app to your Raspberry Pi.
Read the article CI/CD for .Net Core app deployment to Raspberry Pi using Bitbucket
The main problem of a CI/CD pipeline – in my opinion – is logging. When it logs too little you don’t know what’s going on, when it logs to much you can’t see the trees to the forest. Having too much logging can seriously impact the effectiveness of your CI/CD pipeline. This script will improve Xunit unit test output.
Read the article Taming Unit Test logging in Docker pipeline for .NET