I try to keep a somewhat sane structure:

• machines: specific configurations for each machine, usually paired with a hardware configuration. This wil mostly import configurations from other files.
• modules: reusable configurations that can be shared between machines.
• secrets: configuration files not meant to be world-readable on the machine.
• packages: package declarations that aren't worth upstreaming

Note that some configuration is based on charvp's nixos-config which is licensed under the Hippocratic License. Hence, assume this repository is dual licensed under the MIT and Hippocratic license. Please refer to charvp's license for more information.