Skip to content
This repository has been archived by the owner on Apr 13, 2019. It is now read-only.

Extract non-vagrant provisioning to a new recipe #11

Closed
phs opened this issue Apr 14, 2016 · 2 comments · Fixed by #12
Closed

Extract non-vagrant provisioning to a new recipe #11

phs opened this issue Apr 14, 2016 · 2 comments · Fixed by #12
Assignees

Comments

@phs
Copy link
Contributor

phs commented Apr 14, 2016

The existing recipes/vagrant.rb has generic elements that we may want in other contexts, and elements specific to vagrant development environments.

Extract the common elements to a new recipe, so we can open the door to other.. environments?

@phs
Copy link
Contributor Author

phs commented Apr 14, 2016

Nah, this is still too speculative. I'm sure it'll crop up again eventually.

@phs phs closed this as completed Apr 14, 2016
@phs phs added the wontfix label Apr 14, 2016
@phs phs reopened this Apr 14, 2016
@phs
Copy link
Contributor Author

phs commented Apr 14, 2016

Haha, totally need it now.

@phs phs removed the wontfix label Apr 15, 2016
phs added a commit that referenced this issue Apr 15, 2016
Project generation from the template is left in `recipes/vagrant`, but installed packages and `bundle install` move to common.

closes #11
@phs phs self-assigned this Apr 15, 2016
@phs phs closed this as completed in #12 Apr 15, 2016
phs added a commit that referenced this issue Apr 15, 2016
Extract `recipes/common.rb`.
@phs phs removed the in progress label Apr 15, 2016
phs added a commit that referenced this issue Apr 16, 2018
phs added a commit that referenced this issue Apr 16, 2018
Bump `vendor/infrastructure`.
phs added a commit that referenced this issue Apr 16, 2018
phs added a commit that referenced this issue Apr 16, 2018
phs added a commit that referenced this issue Apr 16, 2018
Book-specific content is moved under book/, and provisioning is done
over in infrastructure.

Closes #11
phs added a commit that referenced this issue Apr 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant