deploy-rs/src, branch master forked from https://github.com/serokell/deploy-rs/ [#201] Deduce profile directory during activation 2023-09-12T10:00:17+00:00 Roman Melnikov 2023-09-06T12:54:22+00:00 f26e888c41d28107de9dbc5b4e1553c1dfcf83db Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However, 'deploy-rs' still expects profiles to be present in '/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a profile with newer nix may fail with an error about non-existing files. Solution: Instead of deducing the profile path prior to ssh'ing and actual activation, deduce the path to the profile during as a part of 'activate-rs' invocation. Now if the profile path is not specified explicitly as an attribute in profile within the deploy flake, the path to the profile is determined based on the user to which the profile belongs and on the values of 'XDG_STATE_HOME' and 'HOME' variables. Additionally, if the old profile directory (in '/nix/var/nix/profiles/per-user') for a given user already exists, it is used instead for the sake of backward compatibility. 
Problem: Since https://github.com/NixOS/nix/pull/5226 nix profiles for
users are stored in 'XDG_STATE_HOME' or 'HOME' directory. However,
'deploy-rs' still expects profiles to be present in
'/nix/var/nix/profiles/per-user'. As a result, an attempt to deploy a
profile with newer nix may fail with an error about non-existing files.

Solution: Instead of deducing the profile path prior to ssh'ing and
actual activation, deduce the path to the profile during as a part of
'activate-rs' invocation.

Now if the profile path is not specified explicitly as an attribute in
profile within the deploy flake, the path to the profile is determined
based on the user to which the profile belongs and on the values of
'XDG_STATE_HOME' and 'HOME' variables.
Additionally, if the old profile directory (in
'/nix/var/nix/profiles/per-user') for a given user already exists, it is
used instead for the sake of backward compatibility.
actually merge confirm_timeout into merged_settings 2023-06-08T08:33:01+00:00 Artemis Everfree 2023-06-08T08:33:01+00:00 f28f8c6063dfdee3720a8841cc857df2c911dec8 






Merge pull request #203 from serokell/rvem/#202-add-workaround-for-derivations-store-paths-interpolation
2023-05-08T03:05:03+00:00

Roman Melnikov

2023-05-08T03:05:03+00:00

64160276cd6569694131ed8864d4d35470a84ec3

[#202] Provide '^out' suffix for deriver on newer nix




[#202] Provide '^out' suffix for deriver on newer nix






fixup! [#202] Provide '^out' suffix for deriver on newer nix
2023-05-05T07:04:26+00:00

Roman Melnikov

2023-05-05T07:04:26+00:00

c17d71fadf9a124ad6dd6af91944dbc2f0a60496












[#202] Provide '^out' suffix for deriver on newer nix
2023-05-05T06:57:31+00:00

Roman Melnikov

2023-04-18T07:28:39+00:00

e3bc066bd8f2bcf8433616b7610ef59ba04b679e

Problem: Since 2.15 nix no longer reference '.drv' as derivation
outputs. At the same time, nix before '2.13' doesn't support '.drv'
special suffix handling.

Solution: Provide '^out' suffix for the profile deriver in case
'nix path-info <...>.drv' returns the same '<...>.drv' path.
In other cases either an error about the build result not being present
in the /nix/store is returned or an actual build result path is
returned.





Problem: Since 2.15 nix no longer reference '.drv' as derivation
outputs. At the same time, nix before '2.13' doesn't support '.drv'
special suffix handling.

Solution: Provide '^out' suffix for the profile deriver in case
'nix path-info <...>.drv' returns the same '<...>.drv' path.
In other cases either an error about the build result not being present
in the /nix/store is returned or an actual build result path is
returned.







Merge pull request #205 from serokell/rvem/improve-temp-path-handling
2023-05-05T02:53:03+00:00

Roman Melnikov

2023-05-05T02:53:03+00:00

6b0b6a1c2527e8b1ef370a308b6ef8903004ac47

[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String'




[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String'






[Chore] Handle 'temp_path' as an actual 'Path' instead of 'String'
2023-04-20T07:13:13+00:00

Roman Melnikov

2023-04-19T09:46:43+00:00

784e9ee24d977c99dcb5ba5aef81dae48cb899fb

Problem: 'temp_path' and 'lock_path' are handled as 'String'.
This can be a problem when the 'temp_path' directory is a symlink
on the target system, e.g. this is the case with the default
'/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'.

Solution: Handle 'temp_path' and 'lock_path' as actual Paths.
Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking
filesystem events.

As a side effect, also update the 'notify' dependency to the latest stable version.





Problem: 'temp_path' and 'lock_path' are handled as 'String'.
This can be a problem when the 'temp_path' directory is a symlink
on the target system, e.g. this is the case with the default
'/tmp' and macOS, where this directory is actually a symlink to '/private/tmp'.

Solution: Handle 'temp_path' and 'lock_path' as actual Paths.
Also, canonicalize 'temp_path' to avoid canary file path mismatches when checking
filesystem events.

As a side effect, also update the 'notify' dependency to the latest stable version.







[#197] Fix hostname overriding for remote builds
2023-04-14T05:44:09+00:00

Roman Melnikov

2023-04-14T05:44:09+00:00

55aac55cfafec93938e19a6b475142d81110b3d4

Problem: '--hostname' is ignored when used with '--remote-build'.

Solution: Account for 'data.deploy_data.cmd_overrides.hostname' when
building a profile remotely.





Problem: '--hostname' is ignored when used with '--remote-build'.

Solution: Account for 'data.deploy_data.cmd_overrides.hostname' when
building a profile remotely.







Build every profile first, then push (#158)
2022-12-29T15:19:59+00:00

2xsaiko

2022-12-29T15:19:59+00:00

a5619f5660a00f58c2b7c16d89058e92327ac9b8

Try to build everything first before pushing to remotes. Since the build
is more likely to fail than the upload, if there is an error the deployment
will fail sooner and before uploading any potentially unusable configuration.




Try to build everything first before pushing to remotes. Since the build
is more likely to fail than the upload, if there is an error the deployment
will fail sooner and before uploading any potentially unusable configuration.






Merge pull request #176 from Ma27/activate-boot
2022-12-29T14:25:47+00:00

Alexander Bantyev

2022-12-29T14:25:47+00:00

3878dd40f622d327ee912e9b4077909834261772

Add new activation strategy `boot` as equivalent to `nixos-rebuild boot`




Add new activation strategy `boot` as equivalent to `nixos-rebuild boot`