NixOS daily driver
Find a file
2024-02-02 23:27:44 +01:00
doc flake: pull in changes from digga upstream 2023-03-27 13:43:33 +02:00
hosts feat: fae and paperless-ngx 2024-02-02 23:25:54 +01:00
lib feat: convert to flake-parts 2023-11-10 19:48:06 +01:00
modules feat: more git aliases, nodejs_20 2024-02-02 23:27:44 +01:00
overlays chore: remove overlays for element-,signal-desktop 2024-02-02 23:23:13 +01:00
pkgs feat: init working prison-break 2024-02-02 23:24:16 +01:00
secrets chore: update environment secrets 2024-01-25 19:08:34 +01:00
tests zsh: remove leftover files and traces of zsh usage 2023-05-06 15:19:08 +02:00
users feat: fae and paperless-ngx 2024-02-02 23:25:54 +01:00
.drone.yml fix: move pre-commit treefmt hook into CI 2023-07-13 17:05:27 +02:00
.editorconfig fix: move pre-commit treefmt hook into CI 2023-07-13 17:05:27 +02:00
.envrc nix-direnv: use flake-aware version 2.0.0 2022-04-26 11:36:40 +02:00
.git-blame-ignore-revs Ignore treefmt commit 2022-11-20 23:30:58 +01:00
.gitignore feat: convert to flake-parts 2023-11-10 19:48:06 +01:00
bors.toml bors.toml: don't delete merged branches 2021-05-14 22:49:39 -07:00
CHANGELOG.md Run treefmt command 2022-11-20 23:28:23 +01:00
CONTRIBUTING.md fix: move pre-commit treefmt hook into CI 2023-07-13 17:05:27 +02:00
COPYING init 2019-12-02 22:18:30 -07:00
default.nix flake: pull in changes from digga upstream 2023-03-27 13:43:33 +02:00
flake.lock chore: update flake inputs 2024-01-25 19:22:34 +01:00
flake.nix feat: fae and paperless-ngx 2024-02-02 23:25:54 +01:00
LICENSE.md Run treefmt command 2022-11-20 23:28:23 +01:00
README.md flake: git.b12f.io -> git.pub.solar, bump flake 2023-03-27 10:39:10 +02:00
treefmt.toml lint: exclude file generated by nvfetcher 2023-05-05 18:32:40 +02:00

PubSolarOS

Welcome to PubSolarOS, a very opiniated Linux (NixOS) distribution for the nerdy.

We're creating this distribution for our own personal use and fun, but take pride in our craft. As of 14.08.22 it's running on 14 physical devices, both x86_64 and aarch64.

At its core, it's a NixOS installation running our configuration. The UX decisions and the way the project is structured are what make it PubSolarOS:

  • Reproducibility is king, and the future is with declarative and functional programming. Even if Nix does not turn out to be the end-all-be-all of reproducible package management (Guix looks good), it has a plethora of packages, a very active and helpful community, and very solid software engineering practices.
  • Because reproducibility is king, we're using nix flakes for locking flake dependencies. Digga is our flake utility library, made by the wonderful people of the Divnix community.
  • Physical devices are not shared anymore nowadays. Only seldomly will you find shared devices that need more than one user account. For this reason, only one user (excluding root) is assumed.
  • Keyboard navigation wins where it matters; ergonomics, programmability, efficiency, and speed. We use a tiling window manager (sway) and prioritize cli-based solutions where sensible. The editor is neovim configured to be just as opiniated as the operating system it is a part of. For mailing, neomutt is the default, but we're more divided on that part.
  • We like new and shiny things, so we've moved to Wayland and pipewire.
  • SICHERHEIT is written in capital letters at pub.solar, so we have first- class disk-encryption support. Currently in the works is a paranoid mode where the device can only hibernate (no more sleep or lockscreen) so your data is locked any time you leave the device.
  • Free software is better. If we can avoid it, nonfree software is avoided. By default, allowUnfree is false so we don't ship non-free software in a basic PubSolarOS ISO. However, nothing prevents you from using as much non-free software as you like.
  • Automation is better. The reproducibility of nix feels so much more powerful once you're deploying your new configuration from your laptop to all your other devices with one command. We have an automated CI using drone.
  • Community is important. We just like working on this together, and it feels really good to see our progress at the end of a hakken.irl session.

To get started, take a look at the quick start guide in our docs.