Fedi Jamoussi eljamm

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

Be Careful with Table Driven Tests and `t.Parallel()`

We Gophers, love table-driven-tests, it makes our unittesting structured, and makes it easy to add different test cases with ease.

Let’s create our table driven test, for convenience, I chose to use t.Log as the test function. Notice that we don't have any assertion in this test, it is not needed to for the demonstration.

func TestTLog(t *testing.T) {
	t.Parallel()

Get a DDNS up and running with DuckDNS - Step by Step

Understanding DDNS

In summary, DDNS stands for Dynamic DNS. DDNS updates a DNS name in real-time to point to a changing IP address. This is useful for devices without a static IP. For example, companies like Google use static IPs and IP ranges, which are more expensive than ephemeral IPs and IP ranges. DDNS provides a cost-effective alternative, linking a hostname to a dynamic IP address.

How Does DDNS Work?

To use DDNS, you need an account with a DDNS provider. While some services are paid, they are still cheaper than static public IPs from ISPs. A script or service on your device updates the DDNS server with your current IP at regular intervals to maintain the link between your hostname and IP address. Luckily for us, DuckDNS is free for everybody and relays on donations to keep their services running.

Setting up qemu VM using nix flakes

Did you know that it is rather easy to setup a VM to test your NixOs configuration?

Create simple flake:

# flake.nix
{
  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";

If you want to probe a nix flake and figure out what it exposes, I typically just load it into nix repl and then tab complete around until I find what I'm looking for. E.g.:

$ nix repl
Welcome to Nix 2.18.5. Type :? for help.

nix-repl> :lf github:wez/wezterm/main?dir=nix
Added 12 variables.

	# I used this shell.nix to build LineageOS 13.0 for my maguro (Samsung Galaxy Nexus GSM) phone
	# The build instructions for normal Linuxes are here: https://wiki.lineageos.org/devices/maguro/build
	# For NixOS, follow those instructions but skip anything related to installing packages
	# Detailed instructions:
	# cd into an empty directory of your choice
	# copy this file there
	# in nix-shell:
	# $ repo init -u https://github.com/LineageOS/android.git -b cm-13.0
	# $ repo sync
	# $ source build/envsetup.sh

	--[[
	mpv dynaudnorm filter with visual feedback.

	Copyright 2016 Avi Halachmi ( https://github.com/avih )
	Copyright 2020 Paul B Mahol
	License: public domain

	Needs mpv with very recent FFmpeg build.

	Default config:

	name: Security audit
	on:
	schedule:
	- cron: '0 0 * * *'
	push:
	paths:
	- '**/Cargo.toml'
	- '**/Cargo.lock'
	jobs:
	security_audit:

	image: "rust:latest"

	default:
	before_script:
	- rustc --version
	- cargo --version

	stages:
	- test