curlable install of static binary

[srid]

Let's provide a command like the following the installs omnix:

curl --proto '=https' --tlsv1.2 -sSf -L https://install.omnix.page/cli | sh -s -- install

We need to figure out where to upload the binary, and how to serve it.

(This not high priority or critical for MVP; since it will be less useful without #206 anyway)

[srid]

Another reason for having curlable static binary is that to run the health command itself, the user may end up compiling omnix from scratch, because they haven't added themselves to trusted-users yet (which health will catch, but only in future).

I noticed this during https://x.com/sridca/status/1834327210301210873

[shivaraj-bh]

#277 paves the way to ship a curlable static binary

Edit: To be specific, by removing the need to ship the forked nix static binary

[srid]

Another reason for having curlable static binary is that to run the health command itself, the user may end up compiling omnix from scratch, because they haven't added themselves to trusted-users yet (which health will catch, but only in future).

I noticed this during https://x.com/sridca/status/1834327210301210873

This should help in the meanwhile:

nixos-asia/website@facef6e

[srid]

One issue with curlable install is - how do we deal with upgrades down the line?

We don't want people to be stuck with old version of Omnix. With nix-dev-home, this is not an issue, as they can always update their flake inputs; at the slight inconvenience of 4 unnecessary prompts during initial setup (srid/nixos-unified#66).

---

Thinking aloud, what if we just provided this script:

https://gist.github.com/srid/24f6a25b942699291751d034ba089574

https://github.com/juspay/nixone

New folks with their new macbooks would then just run this command and setup everything up.

We will also have to deal with moving of dotfiles away: juspay/nixos-unified-template#11

[shivaraj-bh]

Should we close this as not planned?