meterriblecrew
/
modules
generated from meterriblecrew/flake-template
3
0
Fork 0
Code Releases Activity
NixOS modules that are too specialized to fit nixpkgs.
5 Commits
1 Branch
0 Tags
41 KiB
Nix 57.5%
Shell 38.5%
Stata 4%
 
 
 
Go to file
Michael Raitza 3752f48666 Fix toolchain 2020-12-02 23:50:04 +01:00
tinydns Add tinydns module 2020-12-02 22:45:10 +01:00
tmp Fix toolchain 2020-12-02 23:50:04 +01:00
.gitignore Initial commit 2020-12-02 18:51:52 +01:00
README.org tinydns: Update README 2020-12-02 23:28:57 +01:00
do Initial commit 2020-12-02 18:51:52 +01:00
flake.lock Add tinydns module 2020-12-02 22:45:10 +01:00
flake.nix Add tinydns module 2020-12-02 22:45:10 +01:00

README.org

NixOS Modules

Modules

tinydns

A replacement for the upstream tinydns module. This module extends the service in an incompatible way. You instantiate a service by adding an attribute <ipv4-address> under services.tinydns. This flake comes with an extended lib attribute, which you must use in your nixos configuration (e.g. in the call to nixpkgs#lib.nixosSystem) to have special functions under lib.tinydns available that create tinydns records from functions and arguments. See the module documentation for currently available functions.

Development

This comes with a self-contained redo toolchain to help in working with the flake. It basically deploys any input flake into the tmp directory for easier access.

redo targets under tmp/ come in three kinds:

clean
will remove all build products under tmp/
<flake>
will make sure a store path to <flake> exists and puts an indirect root into tmp/<flake>.
<flake>.rw
will make sure a store path to <flake> exists and will copy its contents to tmp/.<flake>.rw and will link to it from tmp/<flake>.rw. (Rationale: On Linux, directories cannot denote reliable targets due to their non-trivial relation to modification time.)