Experimental NixOS repo
Find a file
2022-08-14 20:25:12 +02:00
.drone Drone: follow new upstream default branch main, cron fixes (#30) 2021-10-05 19:32:54 +00:00
.github workflows: switch to new default branch main 2021-10-21 18:28:12 -05:00
doc Improve help and screen recording keybindings in sway 2022-08-14 18:03:32 +02:00
hosts Working drone-exec-runner 2022-08-14 20:25:12 +02:00
lib Make check work 2021-10-24 22:03:28 +02:00
modules Fix path in drone runner exec 2022-08-14 20:24:50 +02:00
overlays Merge remote-tracking branch 'origin/main' into b12f 2022-08-14 17:50:21 +02:00
pkgs Fix path in drone runner exec 2022-08-14 20:24:50 +02:00
profiles Merge remote-tracking branch 'origin/main' into b12f 2022-08-14 17:50:21 +02:00
secrets Working drone-exec-runner 2022-08-14 20:25:12 +02:00
shell tree: remove bud and all mentions of it 2022-08-14 17:16:54 +02:00
users Working drone-exec-runner 2022-08-14 20:25:12 +02:00
.drone.yml Remove bud from CI, too 2022-08-14 17:16:56 +02:00
.editorconfig Initial b12f commit 2021-05-30 21:33:09 +02:00
.envrc direnv: update envrc 2022-04-30 15:58:00 +02:00
.gitignore modules: remove redundant server module, SSH is enabled in core profile, too 2021-10-23 23:28:42 +02:00
bors.toml bors.toml: don't delete merged branches 2021-05-14 22:49:39 -07:00
CHANGELOG.md Update Changelog for tag 2021-05-27 17:02:40 +00:00
COPYING init 2019-12-02 22:18:30 -07:00
default.nix default.nix: fix path to compat 2021-05-16 10:22:40 -07:00
flake.lock Merge remote-tracking branch 'origin/main' into b12f 2022-08-14 17:50:21 +02:00
flake.nix Use correct sshUser for droppie deployments 2022-08-14 19:24:12 +02:00
LICENSE.md Add AGPLv3 License 2022-08-14 14:11:10 +02:00
README.md readme: add link to https://ci.b12f.io 2022-08-14 14:41:20 +02:00
shell.nix lib: move compat to lib 2021-04-18 20:51:47 -06: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.