- Fix Listen usage, to support Vagrant 1.7.3, which updated its dependency from 2.8.0 to 3.0.2 [52d9f84]
- Load nvm in non-interactive shells, install bundler in provisioner [fde6873]
- Fix status command [07741d6]
- Update start messages to reflect new script names [565ac76]
- Use site's node and npm versions from package.json [a3f4c19]
BREAKING CHANGES:
- The default Node version goes from
0.10.22
tostable
- The default npm version goes from
1.3.14
to^2.0.0
- Use npm scripts instead of grunt [a626484]
- Create/update site from specific tag on cloned template repo [1b3075b]
BREAKING CHANGES:
- vagrant-solidus no longer manages the Solidus sites using the
grunt
command line. Instead, each site is started directly with its local Solidus bin (./node_modules/.bin/solidus
). For sites that need to compile assets and run a file watcher, new scripts need to be added to theirpackage.json
files. For example, existinggrunt
tasks can still be used, but they need to be called directly with the two new special npm scripts:
{
"scripts": {
"build": "./node_modules/.bin/grunt build",
"watch": "./node_modules/.bin/grunt watch"
},
"devDependencies": {
"grunt": "~0.4.1",
"grunt-cli": "~0.1.13"
}
}
- Restore Vagrant >1.6.3 support [460291e]
- Configurable ports [280de56]
- Add support for Solidus log server [8d5ffb8]
- Restrict to Vagrant 1.5.x until this is resolved: hashicorp/vagrant#3769 [72410cf]
- Initial release
BREAKING CHANGES:
- If you have an old version of solidus-devbox, it's simplest to reset the whole box (this will not remove your sites' files):
$ vagrant destroy
$ vagrant plugin install vagrant-solidus
$ vagrant solidus-box init # Make sure to reapply your custom changes to the new Vagrantfile
$ vagrant up