abcdw

Nix vs Guix

These are notes to the stream: https://youtu.be/S9V-pcTrdL8

Some notes

• We are not aware of a lot of GNU software available to us.
• Seems that Guix more hacker-friendly/explorable.

General comparsion

Description

Nix

Guix

Comment

tykurtz

GROKKING NOTES

I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.

So below I made a list of leetcode problems that are as close to grokking problems as possible.

Pattern: Sliding Window

• https://leetcode.com/problems/maximum-subarray/ # Close enough
• https://leetcode.com/problems/minimum-size-subarray-sum/

jamesmacfie

How to use

In iTerm2, in the menu bar go to Scripts > Manage > New Python Script

Select Basic. Select Long-Running Daemon

Give the script a decent name (I chose auto_dark_mode.py)

Save and open the script in your editor of choice.

KrishnaPravin

How to create an HTTPS certificate for localhost domains

This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.

Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).

afloesch

Jenkins in Docker (docker-in-docker)

Testing Jenkins flows on your local machine, or running Jenkins in production in a docker container can be a little tricky with a docker-in-docker scenario. You could install Jenkins to avoid any docker-in-docker issues, but then you have Jenkins on your machine, and the local environment is likely going to be a fairly different from the actual production build servers, which can lead to annoying and time-consuming issues to debug.

Build environment differences are precisely why there is a strong argument to be made to run build processes strictly in docker containers. If we follow the philosophy that every build step or action should run in a docker container, even the Jenkins server itself, then we get massive benefits from things like, total control over the build environment, easily modify the build environment without the possibility of adversely effecting other jobs, explicit and strongly controlled tool versions,

CMCDragonkai

Journey into Nix Package Repository

There are 2 commits that I need in my build:

• 8d0e3ad603dda85462161bba1351893b84339462
• 83e01aa5e48a9107f3b988c9d4c1c21d610626fb

Clone nixpkgs and add the nixpkgs-channels as a remote.

CMCDragonkai

Nix Overrides

• overrideDerivation is used to override the call to derivation
• overrideAttrs is used to override the call to stdenv.mkDerivation
• override is used to override the last function call. Often this will be the callPackage call.
• overridePythonAttrs is used to override the call to buildPython*.

This PR NixOS/nixpkgs#46842 discusses the idea to have a generic overrideArgs that works like overridePythonAttrs for all language infrastructures.

CMCDragonkai

Understanding Nix Inputs

Every Nix derivation produces a Nix store output that has 3 things:

• Executables
• Libraries
• Data

Executables are always exported using the PATH environment variable. This is pretty much automatic.

CMCDragonkai

#!/usr/bin/env sh

# show the output paths of a derivation
nix-store --query --outputs $(nix-instantiate)
# show the immediate dependencies of a derivation
nix-store --query --references $(nix-instantiate)
# show the transitive dependencies of a derivation
nix-store --query --requisites $(nix-instantiate)
# show the dependers of a store-path
nix-store --query --referrers $(nix-instantiate)

Jomik

{
  coc-nvim = let
    pname = "coc-nvim";
    version = "0.0.61";

    src = fetchFromGitHub {
      owner = "neoclide";
      repo = "coc.nvim";
      rev = "v${version}";
      sha256 = "1as2hb4kfq1m0nq7vp2ibkfq8n219ykr04qx4qadg97s7iky4yx4";