The instructions are a little unclear. The thing to concentrate on is to setup
the vagrant to run your nupic box, then identify the host-machine path to the
shared directory (ie the folder in your real machine which is /vagrant in the
VM). Cd to there on your real machine and do a git clone to get the code.
Now ssh into the VM, and edit your .bashrc so it has the right paths to
/vagrant/nupic (or whatever it is). Run build.sh as per the main readme file
from there and it'll work fine.
Cheapest way to reflect edits to .bashrc is to logout and ssh in again. You
might need to install or update some python modules too. Do this inside the VM.
Regards,
Fergal Byrne
—
Sent from Mailbox for iPhone
On Mon, Oct 28, 2013 at 6:54 PM, Mateja Putic <[email protected]> wrote:
> Vagrant is a virtual machine manager. Virtualbox is one of many virtual
> machine providers compatible with Vagrant. They are separate entities. For
> more info, see the Vagrant docs.
> The Virtualbox machine provided by the nupic project can be configured
> either using Vagrant in the Vagrantfile or using Virtualbox, either through
> the GUI or on the command line.
> If you wish to use Virtualbox to configure the VM, you should add a shared
> folder by Machine > Settings > Shared Folders, then bring the machine up by
> clicking 'Start' in the GUI. Keep in mind, though, that the configuration
> changes you make in Virtualbox will not be reflected in the Vagrantfile,
> because these are separate methods of managing the VM. Since it sounds like
> you already know your way around the Virtualbox GUI, this might be your
> best option to get it running.
> Best,
> --
> Mr. Mateja Putic
> Graduate Research Assistant
> Department of Electrical and Computer Engineering
> University of Virginia
> (703) 303-2099
_______________________________________________
nupic mailing list
[email protected]
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
