Setup instructions not working
See original GitHub issueRunning
curl -Ls fury.build | sh
results in an error
sh: line 1: syntax error near unexpected token `newline'
sh: line 1: `<!DOCTYPE html>'
It looks like fury.build
doesn’t get properly redirected to the setup script file
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Setup instructions are not working for me
So far, I find it very frustraing to setup. I am running on Snow Leopard, using localhost. I have xdebug installed as I...
Read more >Setup instructions result in "create-react-app: command not ...
Following the simple setup instructions yields: -bash: create-react-app: command not found mac os x 10.11.5, node 6.2, npm 3.8.9.
Read more >Basic Self Installation Troubleshooting - Xfinity Support
Basic Self Installation Troubleshooting. Having some trouble installing your Xfinity services after you've moved or received an Xfinity Getting Started kit?
Read more >Turn on and set up iPhone - Apple Support
Prepare for setup On your previous device, go to Settings > General > Transfer or Reset [device]. Tap Get Started, then follow the...
Read more >Spectrum.net Self-Installation Help
Connect Equipment. Your self-installation kit includes step-by-step instructions. You can also view the connection instructions as a video or download the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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 atget.fury.build
and leavefury.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 installedfury
. That is, one purpose of the script is to allow you to runfury
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 withcurl -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.