Closed prolativ closed 3 years ago
I think the IPFS-hosted script file has stopped working. https://fury.build
redirects to an IPFS service if you access it with curl
or wget
, while other browsers will redirect to propensive.com
. It's a bit hacky, but it becomes problematic when one of the servers is down...
It shouldn't be too hard to fix, though.
Does it work for you now, @prolativ?
Downloading the installation script still doesn't work for me when using curl
but it seems to work with wget
. Also running the script without arguments as in the instruction only prints
INFO Launching Fury 0.33.0 in standalone mode...
The project has not been specified.
But running it with system install
args seems to work as expected
That probably means that my browser-sniffing code ("check for curl
in the headers") isn't reliable. It would make much more sense for me to put the script at get.fury.build
and leave fury.build
as the website.
I think that behaviour is expected. IIRC the script detects whether it's being piped, and automatically defaults to system install
, whereas running it will work like an installed fury
. That is, one purpose of the script is to allow you to run fury
without installing it.
This fragile code isn't a great introduction, and you're not the first person to have problems. So I think I'll make the following changes:
get.fury.build
fury.build
HTML page which tells you where to get the scriptcurl -Ls fury.build
and replace them with curl -Ls get.fury.build
I've just fixed the GitHub readme and one other occurrence (which I'm not even sure was linked anywhere). The new domain looks like it is set up now, too.
Running
results in an error
It looks like
fury.build
doesn't get properly redirected to the setup script file