Please tell ^^

I cleaned my bin.

All that’s left is a symlink: sh -> /nix/store/…

Nushell

This is the same setup I’m running, I can highly recommend it.

Nix has an open issue on integrating IPFS support.

There’s also an old tutorial.

Rather the Gestalt of society

+ Impermanence

I use KeePass with three factors:

• The password
• A keyfile I distribute out of band between all hosts that should be able to open the database
• A set of Hardware Keys supporting challange-response

Works really well IMO. I use KeePassXC on Linux and KeePass2Android on Android.

This, or slackhq/nebula

I feel like the floating point suggestion would backfire quickly due to imprecisions.

I mean, it’s a hard problem to solve if you never worked with moduli before.

Nix kann meinem Distro-Hoppen einhalt gewaehren.

That’s the way.

Though you could also use shift to discern between sigterm and sigkill.

This is the Sway

I can’t answer that since I don’t have any cast-enabled devices.

Try Invidious, FreeTube, NewPipe,… All allow you to watch regular youtube content without ads. You can also create instance local accounts to “create playlists” and “subscribe” to people.

sudo-rs

FreeTube has built in SponsorBlock, you can tell it to automatically and seamlessly skip sections of videos, such as sponsors, self ads, intros, outros,…

You’re playing Devils Advocate, and you probaly know it xD

Anyway, I prefer NixOS for it’s declarativity, reproducibility and immutability.

Example: You want nginx with acme setup? Just tell it to, and NixOS will figure out the steps to reach the desired state.

What is the overall goal of this build?

There’s no overall goal to the project. It’s just the result of me tinkering with my systems from time to time (I’m allocating a bit less than three hours each day to coding on personal projects to improve my skills, some of that time flows into my nixos config).

I am very new to nixOS and am interested in it. Specifically for ansible scripts to build out easily replicateable docker hosts for lab.

I’ve extensively used docker/compose before I switched my systems to NixOS, since then I’ve barely touched it.

The thing with Ansible and Docker is that you mostly define the steps you want your systems to automatically go through to reach a specific state.

Nix^[1] approaches the problem the other way around. You define the state you want to have, and Nix solves for the steps that need to be taken to reach that state.

If you want to try your hands at that concept, I recommend installing just Nix on one of your test machines and trying out development shells/devshells with it.

For example the SwayFX repo contains a flake.nix providing a devShell. This allows everyone working on the project to just run nix develop in the cloned repo, or nix develop github:WillPower3309/swayfx without cloning the repo to enter the development environment.

This can be combined with tools like direnv to automatically setup development environments, based on the current directory.

If you want a more encompassing example of what Nix can provide, take a look at:

• nixified.ai
• This presentation by Matthew Croughan on Nix-Flakes and Dockerfiles.

I have also considered it for switching my primary desktop and laptops as being able to have the same OS with everything the way I like it is also intriguing.

While I personally think NixOS is one of the most potent software in existence, and a computer without feels less capable for me, I do not recommend it easily.

Just take a look at hlissner’s FAQ on his system config (which I greatly agree with).

That said, I initially tried NixOS on my PC and pushed the config to a git-forge. I then installed the base NixOS ISO on my laptop and told it to build the config from git. And that worked flawlessly.

In leaving the PC unattended for about 20mins, it went from a full Gnome desktop to my Sway setup.

That’s the point when I was sold.

Sorry for theate response. P.S. I love your wallpaper.

Don’t worry about the late reponse ^^

The wallpaper can be build with nix build sourcehut:~sntx/nix-bg#abstract-liquid btw.