rutrum

What are the advantages/disadvantages of building all my services as nixos modules and running with nixos than just dropping every service in a docker container, managing instead with docker compose and Dockerfiles for each service?

I use nixos btw

Your build might be busted. Mine works with doubletap. I have version 5.7

Oh I've been interested in a mug warmer too. Do you have recommendations?

The lid on this one is a little complicated. Lots of crevices so its hard to clean, and it can be difficult to pour too. Near the end I nearly have to turn it upside down to get the rest out.

This is one of those times I would throw my hands up and look at virtualization instead. Containerization with docker/podman is an option. I recall some time ago there was a utility that sort of embeded different distributions within your own, and you could run commands natively on the host machine but in the environment of the VM. I might also be confusing that with VanillaOS or BlendOS features that have that built in to the OS. APX is VanillaOS's package manager that might be another option, although its getting messy at this point.

Bonus pic with my teacup

I'm currently learning home-manager. There are some configuration options that let you define common program configurations in nix (the language). But those options are limited and might even require package installation.

So for complex (or existing) configs withou package management, you can just tell home-manager explicitly to take dot file at path A (in a git repo, for instance) and link it to path B. This will check for overwrites too, so if path B already exists it will yell at you and no write over existing files, so no sweat.

You can also define different profiles per machine, so if you need something different per machine home-manager can let you do that too. And since its nix, you can break out configuration files as you would in any other language to organize you dotfiles however you like.

There might be something clever in home manager for mapping a file path in your dotfiles repo to the same directory relative to your $HOME, but it's likely you'll just explicitely write something like xdg.configFile.nvim = { source = ./neovim/init.lua; }, mapping precisely each file in your git repo to the appropriate config location.

Let me know if you have other questions. I'm all aboard on the nixos train so I could be bias.

This is certainly an option, just wondering whats done most in practice. Right now this is what my own flakes do.

I'm only just now looking at publishing on flakehub. It does look like many users can point at individual repositories that just package external software. It looks like this encourages a repository for each application. Thanks for suggesting.

I've thought about submitting to the source but I imagine that dumping two files in the root directory for a build tool that the devs don't use or even know about is a hard PR to get merged. But maybe that's not even the optimal way to distribute flakes, and it ought to be in a different place altogether, like nixpkgs or flakehub.

You'd have to explain how gimp doesnt suit your needs, because in the open source world its best in class for photo editing.