Is this not a thing yet? What's the point of a git deploy feature if you can't run post deploy commands like "composer install", "npm run production" and "php artisan migrate"?

+1

Yes I am waiting for this as well! Otherwise might have to start moving completely to Netlify or something similar

+1! I'm waiting this feature to move from Forge to Cloudways.

This is still pending to do? Without this feature the auto-deploy is useless

yes please

eff

vzv

+1 this would save us a lot of time and misery

This is must feature in any basic cloud deploy service, just a textarea for deploy script to run after deploy...

It losses the point if I need to connect via ssh each deployment and run commands manually

Running composer update and Laravel migrations after deployments would be easier with this option.

+1 - This would be great!

Yes please! This would be very useful for automatically running NPM scripts after every deploy.

Maybe you could use git hooks for this. Webhooks don't work for this.

+1. "Deployment via git" functionality is pretty useless without this feature.

Yes, yes, yes! This would allow us to run composer and to be able to not have any dependent packages within our git repo.

And the ability to automatically have this run on a git push of that repo would be awesome.

Yes this would be almost a musthave for us, as after we do a git deploy we want to run Laravel commands line `php artisan route:cache` etc

Please consider adding this feature. Many of my deployments require a Composer or database change so this would be very useful.

This would be great. So after a successful git deployment if I was able to run 'composer install' and 'php artisan migrate' it would give me full automatic deployments.