Skip to content

Conversation

@amitaibu
Copy link
Member

@amitaibu amitaibu commented May 1, 2025

Spotted on a client's project

@amitaibu amitaibu requested a review from AronNovak May 1, 2025 19:07
# Run DB updates.
- exec: drush updb
# Run deploy hooks.
- exec: drush deploy:hook --no-interaction
Copy link
Member

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.

Copy link
Collaborator

@mariano-dagostino mariano-dagostino left a 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.

@AronNovak
Copy link
Member

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants