Standarize post-deployment actions through drush deploy command

Metadrop / scripthor

Swiss knife of scripts for speed up the development on drupal projects.

1 stars 10 forks source link

Standarize post-deployment actions through drush deploy command #11

Closed dlopez-akalam closed 3 years ago

dlopez-akalam commented 3 years ago

See https://www.drush.org/latest/deploycommand/

dlopez-akalam commented 3 years ago

drush deploy command is only present on drush 10.3+ we should check which version of drush is installed on all projects before merging

dlopez-akalam commented 3 years ago

Since the assets are not cached until the site is accessed, I think an extra cache-rebuild isn't really needed. However, if you feel is safer, we could run frontend-build first, and then call drush deploy at the end

dlopez-akalam commented 3 years ago

@rsanzante after merging https://github.com/Metadrop/scripthor/pull/13 , incorporing a new command to import translations could increase the need of an extra cache-rebuild, so we are adding back the extra drush cr call

dlopez-akalam commented 3 years ago

This PR is deprecated because locale-check and locale-import should be applied before config-import, so drush deploy command cannot be used