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
Questions? Need help? Join us on Matrix: [`#yeet:matrix.org`](https://matrix.to/#/#yeet:matrix.org)
14
+
Questions? Need help? Join us on Matrix: [`#yeet:nixos.org`](https://matrix.to/#/#yeet:nixos.org)
15
15
16
16
## Usage
17
17
18
-
Basic usage: `deploy [options] <flake>`.
18
+
Basic usage: `yeet [options] <flake>`.
19
19
20
20
Using this method all profiles specified in the given `<flake>` will be deployed (taking into account the [`profilesOrder`](#node)).
21
21
22
22
Optionally the flake can be constrained to deploy just a single node (`my-flake#my-node`) or a profile (`my-flake#my-node.my-profile`).
23
23
24
24
If your profile or node name has a . in it, simply wrap it in quotes, and the flake path in quotes (to avoid shell escaping), for example 'my-flake."myserver.com".system'.
25
25
26
-
Any "extra" arguments will be passed into the Nix calls, so for instance to deploy an impure profile, you may use `deploy . -- --impure` (note the explicit flake path is necessary for doing this).
26
+
Any "extra" arguments will be passed into the Nix calls, so for instance to deploy an impure profile, you may use `yeet . -- --impure` (note the explicit flake path is necessary for doing this).
27
27
28
28
You can try out this tool easily with `nix run`:
29
29
-`nix run github:serokell/yeet your-flake`
30
30
31
-
In you want to deploy multiple flakes or a subset of profiles with one invocation, instead of calling `deploy <flake>` you can issue `deploy --targets <flake> [<flake> ...]` where `<flake>` is supposed to take the same format as discussed before.
31
+
In you want to deploy multiple flakes or a subset of profiles with one invocation, instead of calling `yeet <flake>` you can issue `yeet --targets <flake> [<flake> ...]` where `<flake>` is supposed to take the same format as discussed before.
32
32
33
33
Running in this mode, if any of the deploys fails, the deploy will be aborted and all successful deploys rolled back. `--rollback-succeeded false` can be used to override this behavior, otherwise the `auto-rollback` argument takes precedent.
34
34
35
35
If you require a signing key to push closures to your server, specify the path to it in the `LOCAL_KEY` environment variable.
36
36
37
-
Check out `deploy --help` for CLI flags! Remember to check there before making one-time changes to things like hostnames.
37
+
Check out `yeet --help` for CLI flags! Remember to check there before making one-time changes to things like hostnames.
38
38
39
39
There is also an `activate` binary though this should be ignored, it is only used internally (on the deployed system) and for testing/hacking purposes.
40
40
@@ -115,7 +115,7 @@ This defines a single node/server, and the profiles you intend it to run.
115
115
hostname = "my.server.gov";
116
116
117
117
# An optional list containing the order you want profiles to be deployed.
118
-
# This will take effect whenever you run `deploy` without specifying a profile, causing it to deploy every profile automatically.
118
+
# This will take effect whenever you run `yeet` without specifying a profile, causing it to deploy every profile automatically.
119
119
# Any profiles not in this list will still be deployed (in an arbitrary order) after those which are listed
0 commit comments