Permalink
Commits on Oct 5, 2011
  1. updated CHANGELOG and README

    rick committed Oct 5, 2011
  2. updated gemspec

    rick committed Oct 5, 2011
  3. fix hashify_domain_filter for ruby 1.9.2

    rick committed Oct 5, 2011
    Ruby 1.8.7 was allowing me to erroneously treat a single string
    (domain name) as an array and call collect on it.  Ruby 1.9.2
    did away with that behavior and exposed a bug in the filter which
    "hashifies" the domain settings from the config file.
    
    Since facon (the mocking library I have been using with bacon, the
    spec library I have been using) is apparently not maintained and
    doesn't work with ruby 1.9.2, I have no easy way to run the test
    suite to see if everything is running in 1.9.2.  I will have to
    do some work to upgrade the test suite to behave under newer
    rubies.
  4. whitespace cleanup

    rick committed Oct 5, 2011
  5. bumping version to 0.6.24

    rick committed Oct 5, 2011
Commits on Sep 29, 2011
  1. Merge branch 'master' into develop

    rick committed Sep 29, 2011
  2. Revert "Merge pull request #24 from sdesbure/master"

    rick committed Sep 29, 2011
    This reverts commit e6190f6, reversing
    changes made to ac8282d.
  3. Merge branch 'release/0.6.23'

    rick committed Sep 29, 2011
  4. update gemspec

    rick committed Sep 29, 2011
  5. Version bump to 0.6.23

    rick committed Sep 29, 2011
  6. update CHANGELOG

    rick committed Sep 29, 2011
  7. update Credits in README.markdown

    rick committed Sep 29, 2011
    @imajes finally getting the credit he's due
  8. README whitespace cleanups

    rick committed Sep 29, 2011
  9. Document which vagrant box we use as "base".

    rick committed Sep 29, 2011
    Presumably we can get better test coverage over time by running against
    various other base boxes.
  10. it's not clear how this ever worked.

    imajes committed with rick Sep 24, 2011
  11. make rsync_changes more robust

    rick committed Sep 29, 2011
    Some versions of rsync report more flags -- let's be more accepting about what we
    recognize.
  12. use ERB in local specs for staleness checks

    rick committed Sep 29, 2011
    Missed this one earlier.
  13. make vagrant RUBYLIB point to wd installation

    rick committed Sep 29, 2011
    So that we automatically get whiskey_disk visible to deployments when running
    integration specs on the vagrant vm.
  14. vagrant now has access to the wd lib

    rick committed Sep 29, 2011
    Sharing this so that we get the effect of having the most recent wd lib
    installed and ready inside the vagrant vm when running integration specs
    (primarily for the 'whiskey_disk/helpers' library specs).
  15. whitespace cleanups

    rick committed Sep 29, 2011
Commits on Sep 28, 2011
  1. Local deployment specs use ERB scenario files

    rick committed Sep 28, 2011
    So that we get a real absolute deployment path no matter where the project is 
    checked out.
  2. spec scenario yml files can now use ERB

    rick committed Sep 28, 2011
    This will make it possible for the local deployment spec to specify a local path
    name that will be absolute, but can vary from installation to installation.
  3. fix local deployment spec target names

    rick committed Sep 28, 2011
    They're never going to match otherwise.
Commits on Sep 25, 2011
  1. Merge pull request #27 from imajes/develop

    rick committed Sep 25, 2011
    Landing pull request to fix issue with most recent jeweler versions.
  2. Merge pull request #24 from sdesbure/master

    imajes committed Sep 25, 2011
    Variable to choose which rake executable to use
Commits on Sep 24, 2011
  1. cleaning up integration spec miscellany

    rick committed Sep 24, 2011
    Mostly it's non-updated hostnames; also whitespace.
    Note that the local deployment spec is horked because of path issues,
    and any specs that rely on the wd gem being installed on the vagrant
    vm are similarly bitched.
  2. We need git and rake installed in our vagrant vm

    rick committed Sep 24, 2011
    Updating the puppet manifest to make this happen.  I'm
    going with "latest" for both of these (including rake, which
    can be a little bitch) until I hear that I need to do something
    otherwise.
  3. make remote deploys work under vagrant for integrations

    rick committed Sep 24, 2011
    We use ssh_options here to point to the vagrant-generated
    ssh_config for use in integration testing (otherwise we can't
    actually get wd to ssh in to our vagrant host).