CODEWITHSUNDEEP
virtual-machinevirtualboxvagrantnupic
srgg6701
srgg6701

Reputation: 2048

Exposing application's codebase to the vagrant instance

I'm trying to run an application using vagrant. I have a directory where the codebase of app is placed and the .vagrant dir that is created there after its initializing. It looks so:

[app_codebase_root]/.vagrant/machines/default/virtualbox

There is a some very short manual about what to do (https://github.com/numenta/nupic/wiki/Running-Nupic-in-a-Virtual-Machine) and I stopped at the point 9 where is said:

9) Expose [app] codebase to the vagrant instance... If you have the codebase checkout out, you can copy or move it into the current directory...

So it's not clear for me what to copy and where? Does it mean some place within vagrant (if yes, then which exactly?) or some another place? Or I should just make a command vagrant ssh now?

Upvotes: 0

Views: 180

Answers (2)

Fergal Byrne
Fergal Byrne

Reputation: 135

This is always going to be a little confusing, so you need to separate the concepts of the host system and the VM.

Let's say the shared directory (the one with the Vagrantfile) is [something]/vagrant on your host system. Copy your app directory to [something]/vagrant/nupic (or run git clone in that directory) while still in Windows. Check using Windows Explorer that you see all the source files.

In a console window, cd to [something]/vagrant and run vagrant ssh.

You are now in the VM, so everything is now the VM's filesystem. Your code is now in /vagrant/nupic. Edit .bashrc as per the instructions to point to this directory, and run the build commands.

Upvotes: 0

Emyl
Emyl

Reputation: 10536

From the Vagrant documentation:

By default, Vagrant will share your project directory (the directory with the Vagrantfile) to /vagrant.

So you should find your codebase root should under /vagrant on your guest.

Upvotes: 2

Related Questions