-
Notifications
You must be signed in to change notification settings - Fork 55
Execute deploy hooks #836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Execute deploy hooks #836
Conversation
.ddev/config.local.yaml.example
Outdated
| # Run DB updates. | ||
| - exec: drush updb | ||
| # Run deploy hooks. | ||
| - exec: drush deploy:hook --no-interaction |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should preserve drush updb, shouldn't we?
Also this should be the last step, after config import, see the Robo logic.
mariano-dagostino
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to run drush updb, deploy:hook includes it as first step.
|
Then should we adapt DeploymentTrait.deployPantheonSync too to do the same logic? |
| # hosting environment won't provide unlimited | ||
| # memory either. | ||
| # @see https://github.com/drud/ddev/issues/1825#issuecomment-529964728 | ||
| - exec: perl -pi -e 's/memory_limit.*$/memory_limit = -1/' /etc/php/${DDEV_PHP_VERSION}/cli/conf.d/*.ini |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit dangerous. We create plenty of Drush commands what will run in a limited environment. So this means a memory-hungry Drush operation will work smoothly locally and fail on Pantheon. I doubt that we want it.
See #838
Spotted on a client's project