vagrant provisioning fails on nginx build about api-umbrella HOT 4 CLOSED

I believe this should be fixed in master. However, there's a new dependency on the vagrant-berkshelf plugin for vagrant, so that will need to be installed first. So to update your current repo, I think you'll need to do something like:

$ git pull # Update your code
$ git submodule update --init --recursive # Update any submodules
$ vagrant plugin install vagrant-berkshelf # Install the berkshelf plugin.
$ vagrant provision # This should pickup with the chef stuff from where it last died.

From there, you should be able to follow the normal setup instructions staring with the vagrant ssh step under Running API Umbrella in the readme.

(Alternatively, you can always do a vagrant destroy and start over with the instructions from the beginning, which might be easier if you hadn't really started yet, but shouldn't strictly be necessary)

For a bit more detail on the fix: I had actually been recently working on moving the Chef dependencies to use Berkshelf. If you're not familiar, Berkshelf is a dependency management tool for Chef. The hope is that it should hopefully make these Chef dependencies a little easier to manage reliably. So the change to the repo is a bit bigger than just fixing this one nginx build issue, but hopefully it should also fix this issue for you. I've been able to successfully provision new VMs from scratch a couple times using the new setup, so I think everything's working now, but since this is a larger change, don't hesitate to reach out if you run into any further issues.

Thanks for the bug report!

from api-umbrella.

Just to confirm: it does indeed work now. Thanks! If I try to point my browser at /admin, however, it redirects to http://api.vagrant which does not exist, but that I guess is another matter. =)

from api-umbrella.

Adding this /etc/hosts entry solved the problem:

10.10.10.2      api.vagrant

from api-umbrella.

Sorry for the delay in following up. Glad you were able to find the /etc/hosts fix. I've updated the README setup instructions to reflect this. However, ideally, I don't actually want this to be a requirement, so I've added a new ticket to fix this at some point: #20.

from api-umbrella.