- making it work with vagrant standalone version 1.2.2 - install gemstone 3.1.0.x versions
Version management of gems with bundler - first stab. I'm starting to look into this. As there is no side effect to be expected I just merge it now
… helpful because vagrant and ruby are brittle when it comes to versions of involved modules
nginx from source, build support and monit startup time. Checked against newest module versions. Still has a culprit saying about invalid date spec in json module.
Needs an update with monit and conditional ports, but I'd rather share it than let it rot away at my machine, and forget how on earth I created that box again...
Extracted from a customer deployment. SSL should also be supported in this build, but is not switched on by default. Possible improvements: * place the nginx_installer directory in the new cache directory (so downloaded files remain between vagrant destroy and up, but is not as much in the way) * move the downloads from nginx_installer.sh, and parse the downloads for the version number; you download whatever.zip, but need to specify whatever345bc6 to make/configure. After a while this build breaks because the version numbers have moved on. * add ssl port to Vagrant (but conflicts easily with other apps, so maybe configurable).
Still needs help though.
It seems the attributes/default.rb is not read. Don't understand why (works on another repository). Help would be appreciated. Worked around it by putting the start delay in the Vagrantfile
so builds and development can start from a box file where everything works. Next step: add rspec to test it actually works before packaging the box.
…rable and configured in Vagrantfile
port 8080 already used by default by many applications (in this case Jenkins, but also Pharo uses it)
uses ruby 1.9.2 use this (with bundler?) to make sure everybody uses the same version of ruby and the same set of gems locally as well as with gemkins. Should e.g. ensure we have a consistent version of chef loaded. Inspired by: * http://jedi.be/blog/2011/03/28/using-vagrant-as-a-team/ * http://blog.8thlight.com/lihsuan-lung/2011/03/02/jenkins-rvm-and-selenium.html * https://rvm.beginrescueend.com/integration/hudson/ * https://wiki.jenkins-ci.org/display/JENKINS/Rake+Plugin
… rest properly loaded
…ble to all other recipes
[refactoring] replaced runit with empty txt file
easier to merge cookbooks / site-cookbooks refactoring.
…th fixed 3.0.5 version instead of latestVersion. gemstone also seems to need an explicit commit, with commitOnAlmostOutOfMemoryDuring
To follow opscode convention. unmodified opscode cookbooks go in cookbooks, locally modified or homebrew cookbooks go in site-cookbooks. Do a vagrant reload for vagrant to pick up new structure, vagrant provision may not be sufficient.
…ced with fixed 3.0.5 version instead of latestVersion. gemstone also seems to need an explicit commit, with commitOnAlmostOutOfMemoryDuring