You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a nix noob I (unnecessarily) struggled with this one, although it's arguably the most logical use case to directly start using nixcloud: a "zero install" method by just referring to the remote repo in the .nix file using nixcloud.
I.e. I would have expected that a solution that does the below is actually documented as the first and preferred "installation" method, since it makes the most sense for remote declarative deployments.
After some trial and horror I ended up with:
{imports=["${fetchGithttps://github.com/nixcloud/nixcloud-webservices}/modules/"];nixcloud.tests.enable=false;# only now can you start using nixcloud.... options}
which arguably doesn't support referring to a specific tag or commit and would therefore be less robust upon rebuilds.
An alternative which also appeared to work is the following, which doesn't have the above problem but is much more convoluted (it could maybe be simplified?):
As a
nix
noob I (unnecessarily) struggled with this one, although it's arguably the most logical use case to directly start usingnixcloud
: a "zero install" method by just referring to the remote repo in the.nix
file usingnixcloud
.I.e. I would have expected that a solution that does the below is actually documented as the first and preferred "installation" method, since it makes the most sense for remote declarative deployments.
After some trial and horror I ended up with:
which arguably doesn't support referring to a specific tag or commit and would therefore be less robust upon rebuilds.
An alternative which also appeared to work is the following, which doesn't have the above problem but is much more convoluted (it could maybe be simplified?):
The text was updated successfully, but these errors were encountered: