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

Pointed the Vagrantfile to a new box with Wordpress 4.4 #385

Open
wants to merge 1 commit into
base: master
from

Conversation

@aulvi
Copy link
Member

@aulvi aulvi commented Dec 11, 2015

Also removed the space from the 'v.name' param, this makes it easier to manage via the command line.

…tches. Also removed the space from the 'v.name' param, this makes it easier to manage via the command line.
@aulvi
Copy link
Member Author

@aulvi aulvi commented Dec 11, 2015

I recommend you vagrant halt and possibly even vagrant destroy before switching to this branch.

@scottgonzalez
Copy link
Member

@scottgonzalez scottgonzalez commented Jan 26, 2016

Is the idea that we'll keep generating new images and changing this script as new versions of WordPress are released?

@scottgonzalez
Copy link
Member

@scottgonzalez scottgonzalez commented Jan 26, 2016

I destroyed my vagrant VM, checked out this branch, ran vagrant up, rebased on top of master, and deployed a site.

The provisioning and deployment worked fine, but I'm still on WordPress 3.8.1. The output from vagrant up does contain Setting the name of the VM: jQuerySites, so it's presumably using the new box.

@JSFOwner JSFOwner removed the CLA: Valid label Nov 5, 2016
@mgol
Copy link
Member

@mgol mgol commented Feb 14, 2018

@aulvi is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants
You can’t perform that action at this time.