0.6.0 (May 13, 2014)
BACKWARDS INCOMPATIBILITY:
- Support for Vagrant < 1.6 has been removed, please try to use a previous plugin version if you can't upgrade.
0.5.1 (May 03, 2014)
BUG FIXES:
- Fix nodejs installation
- Improve usage with vagrant-lxc containers
0.5.0 (Apr 06, 2014)
BACKWARDS INCOMPATIBILITY:
- Support for Vagrant < 1.5 has been removed, please try to use a previous plugin version if you can't upgrade.
- Services / platforms versions are now required to be specified from Vagrantfile to increase reproducibility / reduce the chances of surprises and simplify plugin maintenance.
- All of the services images have been rebuilt from scratch and are now trusted builds.
- The base image for services was changed from Ubuntu Quantal 12.10 to Debian Jessie.
FEATURES:
- Added shortcut for installing multiple ruby / nodejs / python versions from
Vagrantfile
IMPROVEMENTS:
- core: Bumped docker to 0.9.1
- core: Removed dependency on vocker
- core: Simplified usage with vagrant-lxc
- platforms: Improved handling of multiple versions specifications
- platforms: Show message when already installed instead of keeping silent
- platforms/phantomjs: Leverage vagrant-cachier on installation
- platforms/phantomjs: Fix installation of recent versions
- platforms/go: Leverage vagrant-cachier on installation
- platforms/elixir: Fix installation of recent versions
- services/postgres: Rename ventriloquist-pg images to ventriloquist-postgres
0.4.1 (December 13, 2013)
BUG FIXES:
0.4.0 (December 3, 2013)
FEATURES:
- Added support for RethinkDB [GH-4]
- Support for installing guest specific packages (aka
apt-get install) - Introduce
:typeand:vimageparameters for services allowing us to provision multiple containers of the same kind with less pain. - Docker containers are now named after the services configured on the Vagrantfile
BACKWARDS INCOMPATIBILITY:
- All of the services images have been rebuilt from scratch. The reason behind
it is that we inlined
RUNinstructions in order to reduce the amount of AUFS layers and disk space taken by images. - From now on we'll lock Docker installation to a "known to work version"
by default (currently 0.7.0). Things are moving pretty fast over there and it
is pretty hard to keep up with all the changes and to ensure things are
running smooth. You can still specify the version on your
Vagrantfilebut by default it will be a specific version. - The Docker images that make up for services no longer exposes host ports by default in order to aling with Docker's recent changes related to the way exposed ports work.
IMPROVEMENTS:
- core: Bumped vocker dependency to 0.4.0
- core: Provide feedback during provisioning whether a service is already running
- platforms/go: Bumped to 1.2
- platforms/elixir: Bumped to 0.11.2 [GH-34]
- platforms/phantomjs: Bumped to 1.9.2
- platforms/rvm: Install globally [GH-24]
- services: Most images had the
RUNinstructions inlined in order to reduce the amount of AUFS layers - services/elasticsearch: Bumped to 0.90.7
- services/memcached: Bumped to 1.4.15
- services/redis: Bumped to 2.8.2
- services/mysql: Support for 5.6
- services/postgresql: Support for 9.3
- services/postgresql: Make use of packages from http://apt.postgresql.org/pub/repos/apt
instead of the deprecated
ppa:pitti/postgresql
0.3.2 (October 28, 2013)
BUG FIXES:
- Properly escape upstart job parameters
0.3.1 (October 27, 2013)
BUG FIXES:
- Prevent upstart job from respawning all the time and fix issues related to stopping containers [GH-9]
0.3.0 (October 23, 2013)
FEATURES:
IMPROVEMENTS:
- Bump vocker dependency to 0.3.2
0.2.1 (October 12, 2013)
FEATURES:
- Make use of nvm for when installing nodejs, allowing installation of any nodejs version instead of what's available at https://launchpad.net/~chris-lea/+archive/node.js [GH-22]
0.2.0 (October 3, 2013)
FEATURES:
BUG FIXES:
- Bump dependency on Vocker to ~> 0.3.1 in order to fix errors when trying to provision a machine that already have a service / container running.
- Initial public release.