Automation should be at the heart of every software company. If have to configure something manually: script it. Save the script. Use the script. Automate. Anything. Automation. First. Period.
Here I’ll store my notes on WSL tuning. I mainly use WSL to do Dev Containers, so I need it to run as smooth as possible. My main problems include: memory and disk size. Let’s see what we can do to address the problem.
Currently I’m working on a small WordPress plugin that does syntax highlighting. I have the need to ship some maintenance scripts with my Dev Containers. I want some aliases to interact with the scripts (instead of calling them through /scripts/actions.sh. This solution uses a Bash startup file and a custom Dockerfile.
When you host a WordPress website, you might need to have FTP access. If you do FTP, why not SFTP (which uses SSH to do a secure transfer)? It is fully supported by FileZilla. Let’s create a script that does the setup of the new SFTP user. As we’re using WordOps, we’ll grand the new user rights on our /var/www directory.
We 🧡 the combination of Grafana, Hubot & Slack. We use it all the time to visualize dashboards in Slack. But the interaction with certain dashboards might not be as fast as one expect from a chat bot, so let’s see what we can do.
With the Chocolatey Package Manager for Windows, it is super easy to install software from the command-line. This makes your installs scriptable and thus repeatable. In this blog I’ll show you how to render installation instructions from a machine and how to use the Windows Task Scheduler to update your packages regularly.
So far I’ve been using the hubot-pretend package for the testing of the hubot-command-mapper. But as that test package is no longer maintained / updated, I wanted to switch to something that is more in line with what Hubot itself does: hubot-mock-adapter.
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.
At Wehkamp we use many – many – buckets! To do FinOps correctly, it is important we’re able to determine which teams own which buckets. In this article I’ll discuss how to detect Team tags that are not correct and apply the correct ones. We’re using a combination of Bash, AWS CLI, CSV and JQ.