An existing Nix installation has been detected. NOTE: To install Flox using Nix, see https://alpha.floxsdlc.com/docs/tour/tour-1/#download-and-install-flox. Proceeding with this installer will: 1. Remove Nix and its dependency cacert from the default system profile. 2. Replace the Nix daemon with a Flox provided version. 3. Revert any changes the Nix installer made to shell rc files in /etc but backup the current files by adding a .backup-with-nix-before-flox suffix.
I tried following the link but it is dead.
I want to try Flox, but I want to continue to use Nix as I have been until/if I decide to switch entirely to Flox. Is that possible?
Thank you for this feedback! That is indeed a broken link and I have flagged it to be updated. The correct link to use is https://beta.floxdev.com/docs/getting-started/install-flox/. If you have Nix installed (min version 2.7.0) , follow the directions on that page under the Nix/Generic tab to install flox.
The broken link has now been fixed.
Please let us know if you have any other queries re testing flox while maintaining your existing setup.
We look forward to hearing your feedback once you’ve had a chance to play around with it!
thank you for the updates!
re your trusted-substituters query - no, not as long as trusted=1 is used.
re stopping/starting the daemon - yes, it needs root access. Thank you for this feedback as we can tweak the doc to be more clear on this point.
let me expand on @robinbrantley s response to your question about trusted-public-keys
Doesn’t the trusted-substituters name need to match the trust-public-keys
You spotted correctly that most key-names resemble the cache url. However that’s not mandatory, nix will simply try all keys for any substituter.
The names are rather for your convenience to tell them apart and know the purpose of each
Relevant snippet from the docs:
It is used to look up keys on the client when it verifies signatures. It can be anything, but it’s suggested to use the host name of your cache (e.g. cache.example.org ) with a suffix denoting the number of the key (to be incremented every time you need to revoke a key).