If you are a Nix user, you probably already have heard about Nix Flakes. There are already many great posts about it, among them we have the author of flakes - Eelco Dolstra’s
Nix Flakes, Part 1: An Introduction And Tutorial Nix Flakes, Part 2: Evaluation Caching Nix Flakes, Part 3: Managing NixOS Systems I plan to start a new series talking about the more practical side of flakes, i.e. how to use it to solve my day-to-day pain point, one example per post.
A guide to start mining Eth immediately with Nix.
The Goal Web development was fun but setting up the environment can sometimes be tedious because you might need multiple versions of NodeJS installed (hint: not all npm packages are compatible with all versions of NodeJS). Many developers uses nvm to manage their NodeJS versions, and it works great.
However, since we are NixOS fans and Nix itself is a great package management tool, we would like to use it to manage our web development environment as well.
Important Update 2020.05.24 After upgrading to 20.03 version of NixOS, the docker container starts to use the container’s actual name instead of its systemd service’s name to address the container. This means that to specify the database container from the filerun web server’s container, you need to change the value of FR_DB_HOST from docker-filerun-mariadb.service to filerun-mariadb.
The Problem One of the biggest convenience you have in NixOS is that many of the services you want to run are already coded as a “service”.