| .github | ||
| doc | ||
| hosts | ||
| lib | ||
| modules | ||
| overlays | ||
| pkgs | ||
| profiles | ||
| secrets | ||
| shell | ||
| users | ||
| .editorconfig | ||
| .envrc | ||
| .gitignore | ||
| bors.toml | ||
| CHANGELOG.md | ||
| COPYING | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| README.md | ||
| shell.nix | ||
⚠ Advisory ⚠
DevOS requires the flakes feature available via an experimental branch of nix. Until nix 3.0 is released, this project should be considered unstable, though quite usable as flakes have been maturing well for a while.
Introduction
DevOS grants a simple template to use, deploy and manage NixOS systems for personal and productive use. A sane repository structure is provided, integrating several popular projects like home-manager, devshell, and more.
Striving for nix first™ solutions with unobstrusive implementations, a flake centric approach is taken for useful conveniences such as automatic source updates.
Skip the indeterminate nature of other systems, and the perceived tedium of bootstrapping Nix. It's easier than you think!
Status: Beta
Although this project has already matured quite a bit, especially through
recent outfactoring of digga, a fair amount of api polishing is still
expected. There are unstable versions (0.x.x) to help users keep track
of changes and progress.
Getting Started
Check out the guide to get up and running.
Also, have a look at flake.nix. If anything is not immediately
discoverable from there through digga library's mkFlake,
please file a bug report.
In the Wild
The author maintains his own branch, so you can take inspiration, direction, or make critical comments about the code. 😜
Motivation
NixOS provides an amazing abstraction to manage our environment, but that new power can sometimes bring feelings of overwhelm and confusion. Having a turing complete system can easily lead to unlimited complexity if we do it wrong. Instead, we should have a community consensus on how to manage a NixOS system and its satellite projects, from which best practices can evolve.
The future is declarative! 🎉
Community Profiles
There are two branches from which to choose: core and community. The community branch builds on core and includes several ready-made profiles for discretionary use.
Every package and NixOS profile declared in community is uploaded to cachix, so everything provided is available without building anything. This is especially useful for the packages that are overridden from master, as without the cache, rebuilds are quite frequent.
Shoulders
This work does not reinvent the wheel. It stands on the shoulders of the following giants:
🧅 — like the layers of an onion
👪 — like family
❤️
Inspiration & Art
Divnix
The divnix org is an open space that spontaniously formed out of "the Nix". It is really just a place where otherwise unrelated people a) get together and b) stuff done.
It's a place to stop "geeking out in isolation" (or within company boundaries), experiment and learn together and iterate quickly on best practices. That's what it is.
It might eventually become a non-profit if that's not too complicated or if those goals are sufficiently upstreamed into "the Nix", dissolved.
License
DevOS is licensed under the MIT License.