Hi @elephantcoin, there is actually an updated install script tracked in GitHub here BUT I just noticed when testing before sending this that there’s an issue where the tag version number of the releases it downloads now contain a v, e.g. v0.15.0 - until very recently tags were just 0.15.0, so actually that script would have failed anyway.
I’ve uploaded a working script to a new bucket location on S3:
Note that the current CLI user guide actually points to this new S3 bucket (sn-api), not the S3 bucket with an outdated name (safe-api) that you link to in the OP. I assume you got that old link somewhere - let me know where and I’ll update (maybe somewhere on this forum?)
We had deliberately not publicised the new script just yet as we are currently working on a new version of the CLI, authd, etc, that would be compatible with the ongoing/recent refactoring across many of our crates.
I’ll PR the minor change to the GitHub version of the script to take account of the new v in tags (just the addition of a sed command to strip out the v from the version field).
Some extra info…
As alluded to by the folks who jumped in to help above (thanks @folaht and @DeusNexus), there has been fairly vast renaming and refactoring since we last did a release across the board (api, cli, authd, browser, etc) so if you want to see things working together then the install script I’ve updated for you above will install v0.15.0 of the CLI, after that you should follow the instructions from an old version of the CLI readme, say from the v0.15.0 tag here as that has all the correct commands for that version, e.g. safe vault install instead of the new safe node install.
I’m not sure if you’ll hit other issues due to the renaming across the board when you proceed further with this, we’ve really put this to the side and put all efforts into getting out a v0.16.0 and everything that needs to accompany it - ping in here and we’ll do our best to support you if you do need further support.