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

VCCW with 'vagrant up' or 'vagrant up --provision' do not work on a Mac #361

Open
seffw opened this issue Sep 12, 2020 · 1 comment
Open

Comments

@seffw
Copy link

seffw commented Sep 12, 2020

Operating System: Mac OS
Vagrant Version: Latest (12 Sept, 2020)
Virtual Box Version: Latest

I normally love discovering and trying new things, but this has been a mess from the start. I knew I should have bailed after seeing install instructions that just didn't care ("download the zip" - And what? ).

Anyway, after trial and error, figure out I needed to create a directory of my choose, unzip, put the folder contents in that new directory, and then all look good.

Except after all that, on a Mac, it doesn't work.

After using 'vagrant box add vccw-team/xenial64' , If I run vagrant up, I'm told I need to run vagrant provision or vagrant up --provision

None of those work. Nothing is started, no local server is available.

On the first run I had it working, but then the connection went for no apparent reason while I was navigating Wordpress admin. After that, it was the runaround of the 3 commands above.

Before I give up on this, is there any sensible way to make this work on a Mac?

I'm not looking for vagrant destroy then vagrant up. Not only does that not work, but it takes ages and ends up at the same place.

It's clear this is a big issue. You look aroung and see the questions, but there are not solutions out there that I have found. Just vague references to needing to use --provision, but that actually doesn't work (no local server is run). Lets gets some proper Mac instructions out there and save this huge time-waste for those new to Vagrant.

If there's any chance I can figure this out soon, I'll help write some tutorial. I absolutely hate the time that these things waste for other people.

@seffw seffw changed the title 'vagrant up' or 'vagrant up --provision' do not work on a Mac VCCW with 'vagrant up' or 'vagrant up --provision' do not work on a Mac Sep 12, 2020
@adamjgriffith
Copy link

adamjgriffith commented Oct 16, 2020

Hi @seffw, I've been using VCCW on OSX for a long time with no major issues.

Here are the steps I take in settings up a new VCCW repository:

  1. Download and Extract VCCW.zip
  2. Move and rename to a folder of your choosing. I will use ~/Projects/wordpress
  3. Copy ~/Projects/wordpress/provision/default.yml to ~/Projects/wordpress/site.yml
  4. Edit the ~/Projects/wordpress/site.yml
    1. I normally just update hostname and leave the rest
  5. Run vagrant plugin install vagrant-hostsupdater
  6. Run vagrant box add vccw-team/xenial64
  7. Run vagrant up

Now you can use vagrant halt and vagrant up as you like. If you change site.yml you must run vagrant up --provision.

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

No branches or pull requests

2 participants