-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nix flake for dev shell #3702
Conversation
@qwerty287 anything else :) - I kind a need it if i want to dev on my nixos laptop 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No looks good :) (I didn't test it)
Tearing down https://woodpecker-ci-woodpecker-pr-3702.surge.sh |
However, I don't really like having a new config file for every environment. We now have vscode, gitpod, nixos and the "regular" stuff like (Yes, I know that they are all different. VS Code is about installing the extensions there, NixOS about the packages, and Gitpod about a full environment directly usable. Still I don't like it.) |
well i do understand but I would argue that the devs who use the specific thing should just maintain it - and if it's not used we can remove it at some point e.g. wen it not got touched for ~6months or so |
in this case if flake.lock is not updated ... |
Yeah I agree in general but that's not that easy to determine for every environment. A file can be years old and still work flawlessly. Maybe we could use something like codeowners to define maintainers for files if they're external contributors so we also have a list of files like this we could check, but this solution is also not ideal. |
I don't really see why those files have to live in this repo. I have just created a |
because this is a source of truth other who use nix can also revere too - and it does not hurt at all |
Maybe we could use a separate repo where we collect files like this and then link to it from the docs? This way we also don't have to do it for every single repo |
Well this kind a file is ment to be served from the source code repo, if done otherwhise all the tooling around it do not work |
To try it you need nix installed
nix-daemon
running and your user has to be member of the nix-users group. Or use NixOS.then by just:
nix develop -c $SHELL
a dedicated development environment with all needed packages will be created.