Browse files

update vagrant to use virtualenv schematic

fixes #491
  • Loading branch information...
1 parent e7fa306 commit 91a7706ae47207993cabeb8f194bbb46de3fc2b2 @wraithan wraithan committed Nov 5, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 vagrant/bin/
4 vagrant/bin/
@@ -5,8 +5,8 @@ echo "Running ./project/vagrant/bin/"
cd ~/project
echo "Seeding product details JSON..."
-echo 'Checking for DB migrations...'
-python ./vendor/src/schematic/schematic migrations/
+echo "Checking for DB migrations..."
+python schematic migrations/
Mozilla member
kumar303 added a line comment Nov 6, 2012

This should simply be schematic but that won't work until the vagrant install step is updated to use pip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
if [ $? -eq 0 ]; then
echo "Running python runserver"
python runserver

8 comments on commit 91a7706


I'm still getting an error:

vagrant@lucid32:~$ ./project/vagrant/bin/
Running ./project/vagrant/bin/
Seeding product details JSON...
Already seeded product details JSON
Checking for DB migrations...
python: can't open file 'schematic': [Errno 2] No such file or directory

I also tried to run this command manually in the ~/project dir:

vagrant@lucid32:~/project$ python schematic migrations/
python: can't open file 'schematic': [Errno 2] No such file or directory

Not sure what to tell you, that command should be there if you are able to run runserver. My only guess is that your virtualrenv is super out of date and you need to install the requirements after doing a git pull.

Mozilla member

Hi Nate. Ugh, sorry. We had so much trouble with vagrant that it is pretty far out of date now. We hit many vagrant/VirtualBox bugs. Our puppet configs need many updates to get in line with the way you currently install zamboni manually. I'd suggest installing without vagrant.


@natea It isn't really a matter of virtualbox or vagrant versions and more a matter not keeping the recipes used to create the VM up to date since none of us use vagrant for day to day development. Most of us have found it too slow as well as running into a vagrant bug or two.


The only person on the team that uses vagrant at all (that I know of) is @tarekziade. The rest of us find it way to slow so we set up the code base natively. I understand it does lower the barrier for contributors and that is important. But it is also important that we can get things done. If you join the #amo channel on we'll help you get going if you have any questions.


Good to read this, it might be worth updating the docs as well since I spent most of the day working on it only to find this at the end of the day -

Please sign in to comment.