Releases: unleashedtech/deployer-recipes
Releases · unleashedtech/deployer-recipes
0.3.4
Changed
- Defined Drupal private & temporary file paths in default list of
writable_dir_names
.
0.3.3
Changed
- Added the value of
{project}
to the default{environment}_name
variable value to help prevent
host name collisions among similar projects.
0.3.2
Fixed
- Revised Drupal multi-site config to prevent project-specific variables from being overridden.
- Updated WordPress config to be compatible with newer config default values logic.
0.3.1
Fixed
- Revised relevant recipes to be compatible with 7.0.0-rc.3.
- Defining CMS
deploy
task after the majority of the recipes are loaded. fill
functiontrim
compatibility bug fixed.- Revised
release_name
closure to return a string based on timestamp & branch if necessary.
0.3.0
This release adds support for multiple production webservers. In order for such functionality to work, the order of operations for the main deploy.yaml
file needed to be modified. Instead of importing the CMS-related recipe early in the file, it must be imported late. This allows contrib recipes to react to any config that was defined earlier by deploy.yaml
. The earlier approach only allowed global config vars to be overridden.
Changed
- Updated package to use Deployer 7.0.0 release candidate 3.
- Added support for multiple production webservers.
- Revised package to load
config.php
late, instead ofconfig.yml
early.
0.2.1
Changed
- Added
skip_db_ops
option to allow skipping of all DB-related operations. - Added
skip_db_backup
option to allow skipping of DB backup operations.
Drupal
- Added
skip_cache_rebuild
option to allow skipping of cache rebuild operations. - Added
skip_config_import
option to allow skipping of config import operations. - Added
skip_db_update
option to allow skipping of DB update operations. - Added
skip_themes_build
option to allow skipping of theme build operations. - Multi-site support for
cms:drupal:cache:rebuild
. - Multi-site support for
cms:drupal:config:import
. - Multi-site support for
cms:drupal:db:update
.
0.2.0
Changed
Drupal
shared_file_names
now defaults to a single value referencing an.env
file. The
variable can be overridden if standard-fare Drupal configuration via settings files
is preferred. See unleashedtech/dotenv-drupal for more.shared_dir_names
,shared_file_names
&writable_dir_names
now require arrays of
paths relative to the release root. Each path will be parsed for placeholders before use.- The
cms:drupal:db:backup:create
task now supports creating backups of multi-site apps.
Fixed
Drupal
- Database backup(s) are created at the outset of the
deploy
task to help ensure reliability
of the database backup task.
0.1.9
Fixed
- Restoring squashed essential Drupal multi-site variables.
0.1.8
Fixed
- Missing Drupal-init-related import issue fixed.
- YAML script syntax issues resolved.
0.1.7
Changed
- Added Drupal multi-site support.
- Removed database fail-over functionality & added related documentation.
- Renaming keep_backups variable name to backups_limit. Related refactoring.
- Revising dependency version requirements.
- Created releases:cleanup task, which addresses contrib writable files permissions issue.
Fixed
- Fixed additional database backup issue related to standardization of db:backup:download recipes.