-
Notifications
You must be signed in to change notification settings - Fork 15
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
Where-to-build #26
Comments
@infinisil Are you interested in a contribution for this? I'm refactoring my script right that does this, and I'm realizing that it's already decently parameterized and could be potentially ported into |
I had a small IRC conversation on this with @lheckemann: https://logs.nix.samueldr.com/nixus/2020-09-03#1599163378-1599164356; In short:
It would be possible to write a |
Vague wishlisty idea: being able to define where system derivations get built, rather than building them all on the local machine and then having to copy them to the target hosts. Uploading stuff via ADSL sucks.
A simple solution for this would be to allow copying the derivation over and building it on the target machine (or building it on the target machine without creating drv files on the other end; this seems to be possible nowadays?).
But there's all kinds of possibilities to explore in that space, like building on a powerful machine to deploy a tiny cloud server (and have the system derivation copied directly from the powerful machine to the tiny server). Or maybe integration with cachix and/or nix-build.net :^)
The text was updated successfully, but these errors were encountered: