pkgs.package.override - res of lib.makeOverridable (used by callPackage),
overrides arguments of callPackage
https://nixos.org/nixos/nix-pills/override-design-pattern.html
pkgs.foo.override { arg1 = val1; arg2 = val2; ... }
pkgs.package.override - res of lib.makeOverridable (used by callPackage),
overrides arguments of callPackage
https://nixos.org/nixos/nix-pills/override-design-pattern.html
pkgs.foo.override { arg1 = val1; arg2 = val2; ... }
;; Required setup for emacs init file | |
(package-initialize) | |
(require 'org) | |
(require 'org-protocol) | |
;; Set 'my-org-directory' to the base directory of all of | |
;; your org files (with a trailing slash). For me it's: | |
(setq my-org-directory "/scp:org:/home/orgmode/") | |
;; But it could be a local directory for you |
# build python nix shell from a local `./requirements.txt` | |
mkdir ./env | |
cat > ./env/flake.nix << 'EOF' | |
{ | |
inputs = { | |
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; | |
flake-utils.url = "github:numtide/flake-utils"; | |
poetry2nix = { | |
url = "github:nix-community/poetry2nix"; | |
inputs.nixpkgs.follows = "nixpkgs"; |
I've spent the day trying to get this setup working with GitHub and given the number of gotcha's I encountered, it seemed like a good idea to document how I finally got this working with as few hacks as possible. There's a lot of documentation out there (some of it old and misleading) and committing here for posterity will help me remember this when I inevitably need to do this again.
Passwords are simply not enough these days. Regardless of the company, breaches (and the associated Personally Identifiable Information harvested) are a matter of not if, but when. There are a number of things you can do to protect yourself, but being on the tin-foil-hat side of paranoia, means there are a few Commandents that I adhere to (and recommend for other folks)[Insert link to Fight Club Rules for the Secure Internet].
That being said, if you use 2-factor authentication and have committed to using a hardware token such as the Yubikey, then you're already ahead of the curve. The problem is that wh
Setup full disk encryption on a Hetzner cloud CX42 machine. No fancy SSH unlock: you have to go to their web based terminal to enter the disk password on boot.
Notes:
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";
let | |
nixbuildDomain = "eu.nixbuild.net"; | |
nixbuildKey = "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPIQCZc54poJ8vqawd8TraNryQeJnvH1eLpIDgbiqymM"; | |
nixbuildPlatforms = [ "x86_64-linux" "aarch64-linux" ]; | |
nixbuildFeatures = [ "big-parallel" "benchmark" "kvm" "nixos-test" ]; | |
nixbuildSSH = '' | |
Host eu.nixbuild.net | |
PubkeyAcceptedKeyTypes ssh-ed25519 | |
ServerAliveInterval 60 | |
IPQoS throughput |
When I first started to learn how to use NixOS, the Nix package manager, and how to work with the Nix language, I was overwhelmed. While it did not take me too long to (sort of) get into it, it was not the most pleasant experience. I would say that there is not really a single source of truth, like Arch Linux users have with the ArchWiki, where you can basically look up everything. Instead, the information is spread across many different sources, which can make it difficult for beginners to find out how to do what they want to do.
The "modern nix CLI", also known as "nix3 cli", is another thing that can cause confusion when you are just starting your nix journey. There are some commands that look almost exactly the same, such as nix shell
compared to nix-shell
or nix-build
compa
package xyz.faber; | |
import com.fasterxml.jackson.annotation.JsonProperty; | |
import com.fasterxml.jackson.databind.ObjectMapper; | |
import com.fasterxml.jackson.databind.PropertyNamingStrategy; | |
import com.fasterxml.jackson.databind.cfg.MapperConfig; | |
import com.fasterxml.jackson.databind.introspect.AnnotatedField; | |
import com.fasterxml.jackson.databind.introspect.AnnotatedMethod; | |
import com.fasterxml.jackson.databind.introspect.AnnotatedParameter; | |
import org.junit.Test; |