-
Notifications
You must be signed in to change notification settings - Fork 69
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
VVV: Error on install of site-wordpress-meta-environment #148
Comments
I don't know why it would be trying to install the si-contact-form plugin. We don't use it on wordpress.org. |
It may have been used in the distant past, few people have access to update
the list of plugins used in the meta environment
|
It's currently used on jobs.wordpress.net, but was retired from the w.org/plugins repo. @coffee2code, do you want it keep it on production? If so, then maybe the Meta Environment should check out the latest tag via SVN?
I reached out to @tomjn, and he's agreed to help maintain this as a committer 🎉 I'd also be happy to merge a PR that implements whatever Scott thinks is best for Jobs, and grant commit access here to anyone who's already earned Meta commit, and anyone who develops a track record for PRs that are mostly commit-ready out of the box. Having said that, I still think it's probably best to focus most of our energy on site-specific environments. |
I would just remove any reference to the si-contact-form plugin from the meta environment. It's of no critical importance to the jobs site, and its use should get supplanted with something else. In the meantime, its loss is not an issue. |
* remove si-contact-form and fix some permission related problems closes #148 * avoid parameter expansion in jobs provisioner variable strings
I am going through the setup instructions here:
https://github.com/WordPress/contributor-day-handbook/blob/master/*Start%20Here%20-%20General%20Guides/How%20to%20setup%20VVV.md
--->
To enable these environments, check if you have a config/config.yml file in your VVV folder. If you don't have a config.yml file, then run vagrant status and it will be created for you. In config.yml, look for the wordpress-trunk and wordpress-meta-environment and change skip_provisioning: true to skip_provisioning: false and save.
Finally, run vagrant up --provision to apply the change. This will take some time to run, especially if you have enabled the Meta environment.
I changed wordpress-meta-environment:
skip_provisioning: false
Then ran
run vagrant up --provision
I see this in terminal:
@iandunn @tomjn
The text was updated successfully, but these errors were encountered: