This repository has been archived by the owner on Apr 13, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Extract non-vagrant provisioning to a new recipe #11
Labels
Comments
Nah, this is still too speculative. I'm sure it'll crop up again eventually. |
Haha, totally need it now. |
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
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: