I use GNU Stow in order to have important .dot files, usually located in separate directories in the filesystem, version controlled in git from a designated repository. Easier to use a tool like this than to do it manually.

According to the manual:

The command nix-shell will build the dependencies of the specified derivation, but not the derivation itself. It will then start an interactive shell in which all environment variables defined by the derivation path have been set to their corresponding values, and the script $stdenv/setup has been sourced. This is useful for reproducing the environment of a derivation for development.

How does that help me?

I’ve been reading a lot about NixOS lately and wanted to learn more so I’ve took the plunge and now using it as my daily driver. Hopefully I’ll learn more and get a better understanding of it by actually using it. Not sure if I’ll keep it permanently or go back to Fedora Silverblue, but nothing ventured nothing gained.

NixOS, a Linux distribution based on the purely functional package management system Nix, that is composed using modules and packages defined in the Nixpkgs project.

Given that cron is not installed by default on a Fedora Silverblue host, it can either be added as a layered package or you can use systemd which is available by default.

Setting up a local dev environment with Traefik as the proxy has some benefits:

• highly configurable
• only need to expose required ports on the Traefik container
• simplifies configuring SSL certificates and redirects for each dev site.

Given the benefits, I found it worth while investing the time and effort in learning enough about Traefik to apply those benefits to new projects as it simplifies config for each new project.