You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jonpugh Is the Dothooks approach no longer the preferred way of executing deployment commands on the 1.x branch? The module is still there, but there doesn't appear to be a way to enable it in the project or environment settings. I did patch a workaround into our Devshop install, and it seems to function pretty much the same as it did in earlier versions, but if it's going to be removed entirely at some point, I'd rather not do that.
I haven't had much luck using the deploy steps in the composer.json file--the deploy:build step throws an error on new site installations, almost like it's trying to fire before the site is actually installed (interestingly, if the site is already built, the deploy:build step appears to work). I've also tried adding some custom scripts to Composer's standard events (e.g. post-install-cmd), but I'm not sure how best to get the site alias to use for Drush commands going that route.
If you have any advice or info you'd be willing to share, I'd really appreciate it! Thank you.
The text was updated successfully, but these errors were encountered:
@jonpugh Is the Dothooks approach no longer the preferred way of executing deployment commands on the 1.x branch? The module is still there, but there doesn't appear to be a way to enable it in the project or environment settings. I did patch a workaround into our Devshop install, and it seems to function pretty much the same as it did in earlier versions, but if it's going to be removed entirely at some point, I'd rather not do that.
I haven't had much luck using the deploy steps in the composer.json file--the deploy:build step throws an error on new site installations, almost like it's trying to fire before the site is actually installed (interestingly, if the site is already built, the deploy:build step appears to work). I've also tried adding some custom scripts to Composer's standard events (e.g. post-install-cmd), but I'm not sure how best to get the site alias to use for Drush commands going that route.
If you have any advice or info you'd be willing to share, I'd really appreciate it! Thank you.
The text was updated successfully, but these errors were encountered: