This "README" is available in 🇮🇩 Bahasa.
(DRY) - Don't repeat yourself is a principle in software development. We should use this principle to reduce repetitive and time-consuming work. Personally, I just try to apply this principle in my professional and personal work. The most basic example is making these dotfiles, so that I don't have to provide the needs of the devices or tools used in everyday life. So, from this motivation you can see the main goal (Goal).
The work of a software developer, software engineer, or software laborer requires tools that are used on top of a running system (termed an operating system or OS). I am familiar with using operating systems such as OSX based on Darwin/Unix made by Apple and ArchLinux based on Linux. Well my goal is to become a human user agnostic (not religiously attached to a system but still loyal to the creator of the user, except for the operating system made by Mikocok). The tools are collected in one place to store everything about tools, configurations, settings, credentials, and others that support the needs of working or just operating a computer. Where is my container? In this github, then we need git or other tools, which is clear that we stay in sync between each machine we use so that we don't do repetitive things.
To keep it pure and the same between each machine, I decided to use Nix.
Nix is a "purely functional package manager", the Nix experience is completely different than other package managers. For some people it may seem complicated to use, but it is worth it if you understood what you really need.
If you have ever used the "virtual env" tool popular in the "python" ecosystem then you can experience the same thing but across operating systems, platforms, and programming language ecosystems.
Since nix uses functional concepts like declarative then it should be utilized well. such as declaring needs and then declaring with nix language.
Heavily inspired from (malob/nixpkgs) (especially in v1)
This is my personal configuration with nix using flakes, flake.part, home-manager, & nix-darwin for Darwin or MacOS System.
.
├── app/* (Applications, Packages, etc.)
├── nix/* (All nix related files)
├── nix/home (All home-manager related files)
├── nix/hosts (All hosts or machines related files)
├── nix/devShells.nix (All development shells - development environment)
├── nix/nix.nix (Nix CLI configuration)
├── nvim.nix/* (All nix related files for nvim - using [**Nixvim**](https://github.com/nix-community/nixvim))
├── notes/* (All notes with [**Neorg**](https://github.com/nvim-neorg/neorg) format)
├── flake.lock (Flake lock file)
├── flake.nix (Flake file for manage inputs)
If you are not familiar with Nix, it is recommended to read this onboard by zero-to-nix to get started.
But if you want to use Nix, go jump to command below:
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- installClick to expand
| System | Single User | Multiple User | Command |
|---|---|---|---|
| Linux | ✅ | ✅ | Single User • Multi User |
| Darwin (MacOS) | ❌ | ✅ | Multi User |
| More... |
sh <(curl -L https://nixos.org/nix/install) --daemonsh <(curl -L https://nixos.org/nix/install) --no-daemonsh <(curl -L https://nixos.org/nix/install)In general installation of nix, the nix configuration is located in ~/.config/nix/nix.conf.
You MUST be set the experimental-features before use this configuration.
experimental-features = nix-command flakes
// (optional) for distribution cache (DON'T COPY THIS COMMENT LINE)
substituters = https://cache.nixos.org https://cache.nixos.org/ https://r17.cachix.orgAfter you have installed Nix, you can use the following command to clone this repository:
You can use the following nix options on this repository:
nix develop github:r17x/universe#<DEVELOPMENT_ENVIRONMENT_NAME>Note
DEVELOPMENT_ENVIRONMENT_NAME is only available by devShells definitions
nix build github:r17x/universe#darwinConfigurations.$HOSTNAME.system
echo "use flake github:r17x/universe#<DEVELOPMENT_ENVIRONMENT_NAME>" > .envrc
direnv allow
# example:
echo "use flake github:r17x/universe#node20" > .envrc
direnv allow
> node -v
< v20.10.0
# output `result` to `/tmp/result`
nix build github:r17x/universe#darwinConfigurations.$HOSTNAME.system -o /tmp/result
# example: nix build github:r17x/universe#darwinConfigurations.eR17x.system -o /tmp/result
# run `darwin-rebuild switch` to switch to latest build
# and wait until `darwin-rebuild` finish
/tmp/result/sw/bin/darwin-rebuild switch --flake github:r17x/universe#$HOSTNAME
# example: /tmp/result/sw/bin/darwin-rebuild switch --flake github:r17x/universe#eR17x Note
$HOSTNAME is only available by hosts definitions
drb- darwin rebuild aliases - rebuild this nixpkgs.drs- darwin rebuild and switch the build version (make current build to current version of environment).lenv- list of build version<VERSION>, that's usefull for switch aka rollback environment.senv <VERSION>- switch spesific version (number).
- malob/nixpkgs ~ malob Nix System configs!.
- srid/nixos-flake ~ for flake-parts inspiration.