3 ms·

$ ssh brow.sh All of Browsh's servers are currently busy. Please try again soon. Connection to brow.sh closed. Seems like a cool way to do a demo for s

$ ssh brow.sh All of Browsh's servers are currently busy. Please try again soon. Connection to brow.sh closed. Seems like a cool way to do a demo for something that's a bit painful to install on macOS (would love to see $ brew install browsh). I'll have to give it another look once the HN effect has died down.

filleokus 8y ago
For what it's worth, I got the same error, and just downloaded the linked binary [1] and after a quick chmod+x it was up and running (I had a new-ish Firefox in my Applications folder). [1]: https://github.com/browsh-org/browsh/releases/download/v1.2.3/browsh_1.2.3_darwin_amd64 https://github.com/browsh-org/browsh/releases/download/v1.2....
gbajson 8y ago
In my case it generated SIGSEGV and the "Connection to brow.sh" was closed. The more interesting that my gnome-terminal still receives/prints some codes. When I hit enter, it tries to execute them! https://ibb.co/buhqE8 https://ibb.co/buhqE8 and (ENTER) https://ibb.co/itFz7T https://ibb.co/itFz7T Does anyone of you know the mechanism behind it? EDIT: Does anyone of you know how to use it to type into terminal "sudo su -"?
- tombh 8y ago
  This should be fixed in v1.3.2
thomasahle 8y ago
I found that the docker version was the easiest to get running on Mac. It's just `docker run -it browsh/browsh`, and it downloads and runs everything automatically.