This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 181
Development
Fabio Rehm edited this page Jun 3, 2013
·
7 revisions
If want to develop from your physical machine, just sing that same old song:
git clone git://github.com/fgrehm/vagrant-lxc.git
cd vagrant-lxc
bundle install
bundle exec rake # to run unit specs
To run acceptance specs, you'll have to ssh into one of the development boxes and run:
bundle exec rake spec:acceptance
Yes! The gem has been bootstrapped and since you can boot a container from within another, after cloning the project you can run the commands below from the host machine to get a container ready for development:
# Required in order to allow nested containers to be started
sudo apt-get install apparmor-utils
sudo aa-complain /usr/bin/lxc-start
bundle install
cd development
bundle exec vagrant up quantal --provider=lxc
bundle exec vagrant ssh quantal
That should result in a container ready to rock. Once you've SSH into the guest
container, you'll be already on the project's root. Keep in mind that you'll
probably need to run sudo aa-complain /usr/bin/lxc-start
on the host whenever
you want to hack on it, otherwise you won't be able to start nested containers
there to try things out.
bundle install
cd development
# Pass in --provider=virtualbox in case you have VAGRANT_DEFAULT_PROVIDER set to something else
bundle exec vagrant up quantal
# A reload is needed to ensure the updated kernel gets loaded
bundle exec vagrant reload quantal
bundle exec vagrant ssh quantal