-
Notifications
You must be signed in to change notification settings - Fork 101
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
Build on target server? #12
Comments
I suspect this would also help with the separation between target/deploying system as in #13! Very interested in this, especially for machines that are more powerful than distributed builders / my laptop. |
Not yet, but this is definitely on our roadmap. |
Ok. Apart from that the feature set looks interesting. If someone else is looking for this feature as well: Krops does it by default and can be extended to support flakes: https://github.com/Mic92/dotfiles/blob/master/nixos/krops.nix It is also possible to have a krops running the deploy on a remote machine and push the build nixos closure to a another machine. |
Last but not least, it would also enable darwin users to use this! |
Also very interested in this. It would be nice to not need Nix installed at all on eg CI servers that deploy. |
https://github.com/arnarg/pushnix supports this feature. |
Here is my workaround. |
ssh-ng could help here. deploy-rs theoretically supports this today with TL;DR set |
So, I've tried to build it via |
I am using pyinvoke now with a custom task that uploads configuration with rsync and than just run nixos-rebuild in parallel for all my hosts: https://github.com/nix-community/infra#deployment-commands |
Is it possible to build the flake on the targets server instead of my laptop?
I don't want to upload big build closures to my machines all the time.
The text was updated successfully, but these errors were encountered: