Shows how to revert to the less buggy vagrant 0.8!

This commit is contained in:
Kumar McMillan 2012-01-20 15:11:57 -06:00
Родитель ff4b7bf7b2
Коммит 8c8a20c787
1 изменённых файлов: 15 добавлений и 2 удалений

Просмотреть файл

@ -20,13 +20,13 @@ To get started, you'll need:
* The desktop installer walks you through it. * The desktop installer walks you through it.
* `vagrant <http://vagrantup.com/>`_ 0.9 or greater * `vagrant <http://vagrantup.com/>`_ 0.8.10 (not 0.9.*)
* gem is included with Mac OS X. Otherwise you may need to install * gem is included with Mac OS X. Otherwise you may need to install
`Ruby <http://www.ruby-lang.org/>`_ and `gem <http://rubygems.org/>`_. `Ruby <http://www.ruby-lang.org/>`_ and `gem <http://rubygems.org/>`_.
* If it's your first time using Ruby you should probably run * If it's your first time using Ruby you should probably run
``sudo gem update --system`` ``sudo gem update --system``
* To install vagrant run ``sudo gem install vagrant -v '>= 0.9'`` * To install vagrant 0.8 run ``sudo gem install vagrant -v '= 0.8.10'``
If you get stuck, see the Troubleshooting section below. If you get stuck, see the Troubleshooting section below.
@ -133,6 +133,19 @@ Your ``custom.pp`` file is ignored by git.
Troubleshooting Troubleshooting
--------------- ---------------
If you're using vagrant 0.9 you need to downgrade to 0.8.10 because of
`this bug <https://github.com/mitchellh/vagrant/issues/516>`_.
You might see an error like this when first running vagrant::
/Library/Ruby/Gems/1.8/gems/net-ssh-2.1.4/lib/net/ssh/key_factory.rb:38:in `read': Permission denied - /Library/Ruby/Gems/1.8/gems/vagrant-0.8.
It was fixed in `issue 580 <https://github.com/mitchellh/vagrant/issues/580>`_
but until we can run vagrant 0.9 you can fix it with this::
sudo chmod 644 /Library/Ruby/Gems/1.8/gems/vagrant-0.8.10/keys/vagrant
If you have already set up Zamboni with a custom ``settings_local.py`` file If you have already set up Zamboni with a custom ``settings_local.py`` file
then be sure your database credentials match the defaults:: then be sure your database credentials match the defaults::