Envoy no longer uses user's environment by default about envoy

[driesvints]

This doesn't work on 1.4.1 either for me. Afaik you always need to define your server.

[mtnorthrop]

My example was abridged, but there is a server (localhost) defined at the top. I'm sorry for not being more clear.

This is a complete example:

@servers([ 'localhost' => ['127.0.0.1']])

@task('test', ['on' => 'localhost'])
echo $HOME
@endtask

In this case, I would expect the output to be [127.0.0.1]: /home/myusername, the same as if I had created a bash file with the single command echo $HOME.

Instead, there is no output in 1.5.0 because the $HOME variable isn't set, but it does work in 1.4.1.

My solution was to roll back to 1.4.1 and pin the version in my global composer.json file, so my immediate issue is resolved, but it's possible that others might experience this same behavior if they're using 1.5.0 or higher.

Edit: fixed typo in code example

[driesvints]

@mtnorthrop your example still isn't valid. @task('test', 'on' => ['localhost']) isn't valid syntax. Did you try with @task('test', ['on' => 'localhost'])?

[mtnorthrop]

@driesvints I'm sorry, the @task('test', 'on' => ['localhost']) part in the original issue and the comment are both typos; this line is correctly written as @task('test', ['on' => 'localhost']) in my Envoy.blade.php file. I'll edit my issue and comment to fix this.

[driesvints]

Your example works for me on 1.5.0

[mtnorthrop]

Thanks for confirming.

I've just tested again, and the same script works for me on 1.4.1, but still doesn't work on 1.5.0.

As a solution, I'll just keep envoy pinned to 1.4.1 in my global composer.json file.

It's possible that the issue is related to my local configuration or OS, which is Ubuntu 19.04. I hope, at least, that this thread might be useful if someone else runs into the same edgecase that I have.

[boyanraichev]

@mtnorthrop if you have multiple servers defined on several lines it would fail. No new lines should be present in the servers definition - otherwise I was getting the same error