cap "environment" deploy:check should fail if no composer is found

capistrano / composer

Capistrano extension for Composer tasks

MIT License

183 stars 48 forks source link

cap "environment" deploy:check should fail if no composer is found #21

Closed louim closed 9 years ago

louim commented 10 years ago

Hello!

I'm taking a long shot here, as I don't really know how/if this is possible, but I think that deploy:check task should check if there is a composer binary on the server and if it is usable (something like running a composer -v maybe?). Right now, deploy:check just passes, but the actual deploy fail when no composer is found on the server to install packages. What do you think?

swalkinshaw commented 9 years ago

Capistrano v2 had ways to hook into deploy:check to add additional ones. Not sure if that's possible with v3 though. I'll have to look into it.

swalkinshaw commented 9 years ago

Looks like there isn't an easy to do this without rewriting deploy:check.