This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that
| { config, lib, pkgs, ... }: | |
| { | |
| imports = [ | |
| <nixpkgs/nixos/modules/installer/sd-card/sd-image-aarch64-installer.nix> | |
| ./sd-image.nix | |
| ]; | |
| system.stateVersion = "23.11"; | |
| # Pi Zero 2 struggles to work without swap | |
| sdImage.swap.enable = true; |
I wanted to write a module that generates multiple systemd services and timers to scrub some zfs pools at certain intervals. The default scrub config does not support individual scrub intervals for each pool.
I want the config to look like this:
{
services.zfs-auto-scrub = {
tank = "Sat *-*-* 00:00:00";
| { config, pkgs, options, ... }: | |
| let | |
| baseConfig = { | |
| allowUnfree = true; | |
| }; | |
| unstable = import <nixos-unstable> { config = baseConfig; }; | |
| in | |
| { | |
| imports = [ |
This document is targeted at those who seek to build reproducible dev environment across machines, OS, and time.
It maybe easier for remote teams to work together and not spending hours each person setting up asdf/pyenv/rbenv, LSP servers, linters, runtime/libs. Nix is probably the closest thing to Docker in terms of development environment.
Flake is used here because it provides hermetic build, with absolutely no reliance on system environment (be it Arch/Catalina/Mojave). Also it freezes dependencies in flake.lock so builds are reproducible.
This gist provides the setup to develop Java/Clojure/Python applications on Nix. But it can be easily adapted to ruby, nodejs, haskell.
| #!/usr/bin/env python3 | |
| # install dependencies: | |
| # pip install base45 cbor2 (cwt - not used here) | |
| import sys | |
| import zlib | |
| from base45 import b45decode | |
| from cbor2 import loads |
| #!/bin/bash | |
| # otel-cli-ideas.sh - some ideas I'm playing with for otel-cli to cover some | |
| # use cases where manual spans or exec don't quite do the trick | |
| # | |
| # another cool outcome is you could run this without the collector in some | |
| # cases without spamming your OTLP endpoint... | |
| # | |
| # I hope to OSS otel-cli under Apache 2 in early April 2021. | |
| # maybe it could background itself and wait for events on a unix socket? |
| // zig run benchmark.zig -lc -O ReleaseFast | |
| const std = @import("std"); | |
| usingnamespace @import("hashmap.zig"); | |
| pub fn main() !void { | |
| const allocator = std.heap.c_allocator; | |
| var map = try HashMap( |
| from prometheus_client import Counter, start_http_server | |
| from threading import Thread | |
| import requests as re | |
| import time | |
| JOB_NAME = 'test' | |
| INSTANCE = 'localhost' | |
| def scrape_and_send(local_url: str, vm_url: str, scrape_interval: int): |