One more thing -- I've isolated just the relevant commands w/o their output from this file so that you can see exactly what was executed in order to set the vm up:
machine_name:~ user$ hg clone https://bitbucket.org/arches/arches projects/arches machine_name:~ user$ hg clone https://bitbucket.org/arches/cds projects/arches/archesproject/packages/cds machine_name:~ user$ vagrant box add precise32 http://files.vagrantup.com/precise32.box machine_name:~ user$ touch projects/arches/settings_local.py machine_name:~ user$ echo "INSTALLED_PACKAGES = ('cds',)" >> projects/arches/settings_local.py machine_name:~ user$ cd projects/arches machine_name:arches user$ vagrant up machine_name:arches user$ vagrant ssh vagrant@precise32:~$ cd /vagrant vagrant@precise32:/vagrant$ ./runserver-vagrant.sh - Rob On Monday, April 7, 2014 12:03:30 PM UTC-7, Rob Gaston wrote: > > Sorry, I had to clean up and recreate that file; it's no longer available > at that link. It can now be found here: > https://gist.github.com/robgaston/10031103 > > Note: by default the file is being truncated, so click on the link near > the top that says "view the full file" so see the entire file. > > - Rob > > On Monday, April 7, 2014 11:56:27 AM UTC-7, Rob Gaston wrote: >> >> Hi Utsav - >> >> I uploaded a log file showing the entire setup process for creating a >> virtual machine using vagrant on a *-nix system from clone through running >> the development server which you may find helpful. You can find it here: >> >> https://gist.githubusercontent.com/robgaston/10029901/raw/29d58dbe102e060c51fc0aa8dec2e0ff486e3e61/arches_vagrant_setup.log >> >> - Rob >> >> >> On Monday, April 7, 2014 10:55:59 AM UTC-7, Rob Gaston wrote: >>> >>> Hi Utsav - >>> >>> It's hard to say how exactly you've gotten your project folder and >>> virtual machine to this state, but it looks like you've gone wrong >>> somewhere along the line. It would appear that you've got a virtual machine >>> that hasn't been provisioned properly (jdk should have been installed as >>> part of this process for example), but I'm not able to say why. The >>> provisioning process should execute when you run 'vagrant up'. The path to >>> the bash script that performs the provisioning is stored in the >>> VagrantFile. The only thing I could guess is that you've perhaps modified >>> the VagrantFile in a way that changed or bypassed the provisioning >>> process...? >>> >>> I would destroy any virtual machines that you've created, delete your >>> project folder and start over with a fresh clone. I will post the output >>> from a local shell for all the steps from cloning the repo to running the >>> server shortly to demonstrate the proper way to create a development >>> environment using vagrant. >>> >>> - Rob >>> >>> >>> On Monday, April 7, 2014 7:51:58 AM UTC-7, Utsav wrote: >>>> >>>> Hiii >>>>>> >>>>> >>>> <https://lh6.googleusercontent.com/-Vxs8E7UY-Ek/U0K60h599RI/AAAAAAAAAE4/0IqA5o4NFaU/s1600/Screenshot+from+2014-04-07+19%3A37%3A04.png> >>>> >>>> >>>> <https://lh4.googleusercontent.com/-MDPNs7gyKzs/U0K7bgiD_rI/AAAAAAAAAFA/qcRekMB1ggk/s1600/Screenshot+from+2014-04-07+19%3A37%3A12.png> >>>> >>>> I am getting a error when i do ./runserver-vagrant.sh using vagrant >>>> development machine!! Any solutions :( >>>> >>>> >>>> >>>> >>> -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
