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

Add ability to control deployments / updates? #24

Closed
geerlingguy opened this issue Mar 2, 2017 · 4 comments
Closed

Add ability to control deployments / updates? #24

geerlingguy opened this issue Mar 2, 2017 · 4 comments
Labels

Comments

@geerlingguy
Copy link
Owner

@geerlingguy geerlingguy commented Mar 2, 2017

Remaining Tasks

  • Demonstrate POC in a branch (roughly based on Raspberry Pi Dramble playbooks).
  • Rearrange and add documentation on new vars and usage in README.md
  • Add a test to .travis.yml for a Git-based deployment
  • Document new technique upstream in Drupal VM? (See geerlingguy/drupal-vm#1252)

Summary

This role currently is set up to match Drupal VM's main use cases—namely, take an existing Drupal codebase and composer install then drush site-install it, or build a new Drupal codebase using a simple composer.json or drupal.make file, or build a new Drupal project based on the Drupal Composer project, then drush site-install it.

To be what I would term the ultimate Drupal role for Ansible, I want it to also support:

  • Optionally cloning/pulling/otherwise getting a particular Drupal project/codebase onto a server in the docroot/core path.
  • Optionally running a deployment process (defined by the user somehow) when the codebase is updated (e.g. if git pull detects a change).

I've done a bit of work around this for personal projects, and also publicly in the Raspberry Pi Dramble project, but it would be good to wrap that stuff in this role.

Alternatively, if it's more flexible to put things in separate roles, we could break things apart into something like drupal-deploy and drupal-build role... but I'd rather keep things consolidated into this one role.

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Mar 23, 2017

As I'm working through the 'Drupal VM on Production' documentation and preparing a blog post (and maybe screencast) on the topic, I think it's even more relevant to have some deployment mechanism (even if only Git deploys are supported initially) built into the role.

Basically, if you set a git repo, the role will check out that repo into the project root, and then run through the rest of the stuff (Composer build, site install, etc.). And if there's a change, it could run a set of optional deployment things (like updb, config-import, cc, etc.).

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Mar 24, 2017

Working on this now.

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Mar 24, 2017

Working on some tests now.

@geerlingguy

This comment has been minimized.

Copy link
Owner Author

@geerlingguy geerlingguy commented Mar 24, 2017

Added upstream issue in Drupal VM project: geerlingguy/drupal-vm#1252

Everything else looks good. Once tests pass, I'll merge, then do a minor version bump since there are a couple variable changes... though nothing should break because of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.