Skip to content
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

Deploys: Make wp core update-db optional #827

Merged
merged 1 commit into from
Apr 12, 2017

Conversation

fullyint
Copy link
Contributor

On deploys, users with large network databases may want to disable the wp core update-db option to avoid the long processing time.

This PR adds the update_db_on_deploy option variable (default true) to control whether the update-db runs. This var may be defined per site in wordpress_site or just generally in group_vars.

This PR also consolidates the two "Update WP database" tasks, where the only difference was the presence of the --network flag for multisite.

Users with large network databases may choose to
disable this option to avoid long processing time.
@swalkinshaw
Copy link
Member

👍

@fullyint fullyint merged commit f948df1 into master Apr 12, 2017
@fullyint fullyint deleted the conditional-update-db-on-deploy branch April 12, 2017 23:19
primozcigler added a commit to primozcigler/trellis that referenced this pull request Jun 26, 2017
* master: (120 commits)
  Reload Nginx with updates to manual cert or key (roots#843)
  Add self signed certificates subdomains (roots#812)
  Add support for SMTP without authentication
  Remove output about running WP-CLI and Composer
  Option to install WP-CLI packages (roots#837)
  Update WP theme paths only when template_root in releases_path (roots#840)
  Update wp-cli to 1.2.1 (roots#838)
  skip plugins with WP-CLI, to avoid crappy plugins breaking deploys
  Add options for sources and version
  Add re-run vagrant up message
  Remove plugins from README
  Auto-install Vagrant plugins
  Fixes
  Add Vagrant config support
  Use python slice on password salt instead of Jinja2 truncate()
  Avoid single var containing jinja delimiters in when parameter
  Remove jinja delimiters from tasks' when parameter
  Update connection test for new dense.py callback in Ansible 2.3
  Deploys: Make wp core update-db optional (roots#827)
  Use a block
  ...

# Conflicts:
#	Vagrantfile
#	ansible.cfg
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.

2 participants