Hi Phil,
My bet is that your Vagrant version is older than 1.5, in which case you
need vagrant-berkshelf pre-2.0. For example:
vagrant plugin install vagrant-berkshelf --plugin-version ' 2.0'
--
Teemu
On Sat, May 3, 2014 at 12:08 AM, phil swenson phil.swen...@gmail.comwrote:
I am trying
Hello Daniel -
Probably won't find much help here since this appears to be PyCharm issue
and not a Vagrant one. However, I was able to narrow this down to the
--multiproc flag. If manually removed and executed it starts up fine. I
am looking for a way to remove that from PyCharm. Will
Hi,
Just started with Vagrant, and I would like to share how I do wiretapping
of the Vagrant clients. Useful for network debugging. Only prerequisite is
that you have tcpdump on the client and Wireshark on your host. You put the
script in the same directory as your Vagrantfile.
The script
Hi,
I'm porting some code from Vagrant 1.0.x to 1.5.x. The code hooks into the
`up` (new VM is created) and `start` (existing VM is booted) events. In
Vagrant 1.5, I'm seeing machine_action_up, machine_action_halt and
machine_action_provision, which I'm making use of. But I don't see a way to
Hiii,
After configuring a private network with a ip in Vagrantfile .. i was able
to see my files!
Now my browser looks like this! http://apaste.info/OyW
My bootstrap.sh file --http://apaste.info/e6s
In the previous setup , when i ran service apache2 status ... after vagrant
up , apache
Thanks for sharing this Niklas.
Forgive my ignorance but what is the use case for wiretapping the client
(by client I assume you mean guest)?
Thanks,
Robert
On Saturday, May 3, 2014 3:26:40 AM UTC-7, Niklas Andersson wrote:
Hi,
I just started to get acquainted with Vagrant. Great tool,
If you are able to see your files in browser that means apache *is *working
and started.
If you're not seeing the files after restarting your VM it means apache was
not installed as service, you can simply run *`update-rc.d apache2 defaults*`
and add this to your bootstrap for future provisioning.
