Nix package

[XHawk87]

I haven't really tried Nix yet myself, but after reading this discussion I wondered if it would be useful here: https://discourse.nixos.org/t/is-there-much-difference-between-using-nix-shell-and-docker-for-local-development/807

It sounds like it could eliminate a lot of bug reports you get from people saying it doesn't work on their machine. Better than docker, or docker alone.

[Technetium1]

That doesn't usually come without some added maintenance burden itself even in the best circumstances unfortunately. It is technically possible, but do the benefits outweigh the cost? Will that ultimately lead to fewer contributions from the increased difficulty floor? What about more difficulty with prerequisites, since Nix isn't always easy to install?

[XHawk87]

As I say, I am not that familiar with Nix, so I am trying to understand. Some things just aren't adding up for me. I see other projects adding nix support, complex projects with lots of contributions, and most of the maintainers aren't even aware it's on Nix. 2 years and the file sits there without needing any changes with the CI checks passing quietly in the background. Can you explain why this project in particular would be different? Is maintaining a Nix file really that different to a Dockerfile?

[Technetium1]

It can be considered multiple ways. Nix can be used to build the containers (uncommon): https://xeiaso.net/talks/2024/nix-docker-build/. Nix can be used to run the development environment locally, this is much more common: https://github.com/nix-community/nix-direnv. Nix can also be used to distribute a 'final result' more directly: https://wiki.nixos.org/wiki/Flakes

The way the project is now, it is meant to be run via Docker. This means the first part (using Nix to build the containers) is feasible, but it is arguably ineffectual because there isn't really any large change/benefit from doing so. Reproducible builds are conceptually wonderful, but I don't see them as solving an inherent issue here.

In order for the other 2 options to be useful, there should be a supported way to run without Docker, which seems outside the current scope of the project's goals. I would like for it to be an option. Only m1k1o can know if they want to go that direction, because the maintenance burden falls to them, and the current project structure may need changed in some large ways.

[XHawk87]

Very interesting reads! I might well look into building some docker images with it.

I did notice that it is possible but not recommended to run neko without docker: https://neko.m1k1o.net/#/getting-started/faq?id=can-i-use-neko-without-docker

[Technetium1]

I didn't see that was an option at all!!! This just became much more feasible, though the aforementioned caveats do still apply.