envoy self-update returns JSON exception about envoy

[taylorotwell]

Weird. I'm getting it too. Not sure what's up with that.

[taylorotwell]

Do you have the openssl extension installed?

[csoutham]

Hi Taylor, yes it looks like it from phpinfo():
OpenSSL 0.9.8y 5 Feb 2013

[taylorotwell]

What about on the CLI?

[csoutham]

Yes, according to php -i
Same version - should be the same via both as they are calling the same path.
Do you see it as well?

[csoutham]

Don't suppose it's something as simple as a redirect.
The 'broken' manifest does redirect to here:
https://raw.githubusercontent.com/laravel/envoy/master/envoy-manifest.json

[taylorotwell]

That also fails :/

[bretterer]

@taylorotwell Had an issue like this as well on Vaprobash... Recently Github changed the raw url's which required adding in the follow flag for curl. I am not sure how the envoy phar is built really but could it be something like that?

[csoutham]

@taylorotwell This seems to have fixed itself or was potentially an issue with a previous version of MAMP on my set up (although you said it was the same for you).
MAMP Pro PHP v5.4.26 on the CLI seems good to me 👍

[taylorotwell]

I plan to release Envoy as a "global" composer install type package soon, so this whole self-update thing will kind of go away.