You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is specifically a problem for us when trying to clone our decaturmakers.org repo. It happens because the vagrant provisioning process runs as root and doesn't have access to a forwarded SSH agent (During vagrant ssh, SSH agent forwarding does work, but that doesn't help us here). I have two solutions to the problem and thought this would be a good place to discuss, debate and decide on which solution we'd like to use.
Part of the initial setup would require you to create a Personal access token on github.com. We'd then have the vvv-init.sh script clone decaturmakers.org via HTTPS (using the personal access token) for authentication.
Pros
Cons
Everything remains encapsulated in this single vvv-init.sh script
There is an extra initial step of having to generate a personal access token
We use a Makefile to clone the decaturmakers.org repo on the host machine and then run the initial vagrant up. In this scenario the vvv-init.sh script would basically just do the automated WP installs using the wp-cli.
Pros
Cons
Ideally, the initialization of the dev enviroment is a single command: make
Can't really thing of any cons
The text was updated successfully, but these errors were encountered:
I don't have a strong preference for either solution. I'm comfortable with both options. Creating a personal access token on github.com may potentially have additional benefits later but it will be an additional (one-time) step for newbies, too. A Makefile provides potentially more customization down the road but is a more traditional approach and may require installation of CLI dev tools (autoconf, etc?).
I'd say flip a coin or just choose one if there aren't any more opinions in the next day or so.
This is specifically a problem for us when trying to clone our decaturmakers.org repo. It happens because the vagrant provisioning process runs as root and doesn't have access to a forwarded SSH agent (During
vagrant ssh
, SSH agent forwarding does work, but that doesn't help us here). I have two solutions to the problem and thought this would be a good place to discuss, debate and decide on which solution we'd like to use.vvv-init.sh
script clonedecaturmakers.org
via HTTPS (using the personal access token) for authentication.vvv-init.sh
scriptMakefile
to clone thedecaturmakers.org
repo on the host machine and then run the initialvagrant up
. In this scenario thevvv-init.sh
script would basically just do the automated WP installs using thewp-cli
.make
The text was updated successfully, but these errors were encountered: