summaryrefslogtreecommitdiffstats
path: root/vagrant/definitions
Commit message (Collapse)AuthorAgeFilesLines
* Update comment.Tails developers2014-07-111-1/+1
|
* Migrate Vagrant basebox to Debian Wheezy (Closes #7133, #6736).Tails developers2014-07-103-27/+14
| | | | | | | | | | | | | | | | | | | | | | | | This does a number of things beyond upgrading the basebox distribution to Debian Wheezy: * Drop Rakefile integration since it relies on Veewee's integration in Vagrant, which is broken. Now a workaround is documented. * Install the 3.x "from"-port (squeeze's l-b 2.x re-versioned to 3.x to replace wheezy's real 3.x) of `live-build` from deb.t.b.org. * Bump disk capacity to 15 GB to take into account the larger amount of space needed when building Wheezy images (#7133). This should also future-proof this aspect a bit. * The documented process for buliding new baseboxes, in particular the part that gives each one a new name, not only *works* (as opposed to the old docs, and the Rakefile integration) but should also solve #6736. The different name implies that Vagrant won't use the cached version. Of course, the commit that updates the basebox must be present in a branch for it to use the new basebox. * Various small improvements.
* Vagrant: use http.debian.net instead of the mostly broken (and soon ↵Tails developers2013-12-211-2/+2
| | | | obsolete) cdn.debian.net.
* vagrant: Also use our common settings when building baseboxTails developers2012-05-161-1/+4
| | | | "Don't Repeat Yourself!" for the win.
* vagrant: Purge installer log at the end of basebox setupTails developers2012-05-161-0/+3
|
* vagrant: Add task to create our squeeze baseboxTails developers2012-05-162-1/+4
| | | | | | | | | | | | | | | | As we use Veewee to automate the creation of the basebox, we are forced to back up on the "do not execute Vagrant manually" stance. This is due to the fact that Veewee is quite hackish and itself calls `vagrant` directly. So we move our monkey-patching from the Rakefile to the Vagrantfile itself. In order to support an HTTP proxy, the `preseed.cfg` file that Veewee need is created beforehands in another Rake task. Proxies bound to localhost will result in a failure and an explicit error messages. Note: it is unfortunately not possible to use `definitions.rb` to add `mirror/http/proxy` to the installer command-line. As the defined proxy is set by network-preesed, it will prevent the installer from retrieving the preseed file provided by Veewee on a local interface.
* vagrant: Trim and document basebox preseed.cfgTails developers2012-05-161-260/+11
|
* vagrant: 1 GB of RAM is enough for the baseboxTails developers2012-05-161-1/+1
|
* vagrant: Import initial research from todo/build_with_vagrantTails developers2012-05-163-0/+404