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

Chapter 6 drush.yml #366

Open
typ-ex opened this issue Jan 5, 2021 · 3 comments
Open

Chapter 6 drush.yml #366

typ-ex opened this issue Jan 5, 2021 · 3 comments

Comments

@typ-ex
Copy link

typ-ex commented Jan 5, 2021

The playbook gets stuck at "install drush dependencies with composer". Thought it was just me, but I cloned the entire repository onto my machine and same thing.

Ubuntu 20.04, which I don't think is relevant cause it's working via vagrant
Vagrant 2.2.14
ansible 2.10.4

@typ-ex typ-ex closed this as completed Jan 5, 2021
@typ-ex typ-ex reopened this Jan 5, 2021
@typ-ex
Copy link
Author

typ-ex commented Jan 5, 2021

I got it to run, and figured out it got stuck in 2 places, both involving composer

  1. drush.yml - install dependencies with composer. I had to vagrant ssh in, and run sudo composer install to get it to work
  2. drupal.yml - install dependencies with composer. Again had to run sudo composer install to get it to work

It's weird because becoming sudo was already stated at the beginning of playbook.yml, and didn't seem to pass into these tasks.

I also noticed in drupal.yml that ownership was taken by www-data, which might have been done to demonstrate the conditional. While I can confirm that step worked, running it as www-data still didn't work. Again, ended up running sudo composer install to get it running.

edit
Just read that sudo composer install isn't recommended. Not sure what the next best action would be.

Worth noting that the dependencies are newly introduced in this playbook vs the playbook in Chapter 4.

@typ-ex
Copy link
Author

typ-ex commented Feb 10, 2021

Syntax error on my part. Figured out what the original issue was with this. Currently testing fix.

@typ-ex
Copy link
Author

typ-ex commented Feb 10, 2021

Okay. I looked at it again, what a ride.

Turns out while the edits have been made in chapter 4's larger single playbook, the edits haven't made it's way to chapter 6 when it's done again.

What I ended up doing was deleting the drush.yml file entirely, and added the single drush task to the drupal task because it seems like the tasks have a very specific order they need to be done in. An alternative I've entertained is running a check for the file in pre-tasks and establishing the variable there.

Leaving open for other solutions that may fit your coding style better.

@typ-ex typ-ex closed this as completed Feb 10, 2021
@typ-ex typ-ex reopened this Feb 10, 2021
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

No branches or pull requests

2 participants
@typ-ex and others