README.rdoc in fabric-0.2.0 vs README.rdoc in fabric-0.3.0

- old
+ new

@@ -62,30 +62,35 @@ map.grant :all, :all # Create a namespace - this will contain all the users defined in the parent, # but any users and roles added will only exist within this block map.namespace do |cool_website| + # pass multiple IPs to add multiple hosts to this role cool_website.role 'memcached', '1.1.1.1', '2.2.2.2' # This user will only exist within the current namespace cool_website.user 'timmy' # Add all our users, including from the parent, to the memcached server: grant :all, 'memcached' + # Timmy isn't allowed onto the syslogging box :( + cool_website.role 'syslog', '3.3.3.3' + grant "timmy", :all, :except => ["syslog"] + end end -== Normal Requirements +== Testing Requirements -None - this should run straight out of the box. +You want to get involved? Great! Grab the code and check dependencies with: -== Testing Requirements + rake check_dependencies -Bundler (http://github.com/wycats/bundler) is used to manage dependencies, and has cached versions of those gems which are required for execution. For development, it expects those files listed in the Gemfile with :bundle => false to be installed into the version of gems that the gem will run under. +Previously, bundler (http://github.com/wycats/bundler) was used to package dependencies; unfortunately this doesn't seem to play that nicely with jeweler. -The tests for this gem rely on being able to ssh to a target machine. This can be your development machine, but it's easier if it's a Virtual Machine (try out something from http://virtualbox.org). To run tests, first ensure you have bundled the gems with 'gem bundle', and copy the test.yml.example file to point at a machine which can be safely used to test SSH commands. +A lot of the tests this gem rely on being able to ssh to a target machine. This can be your development machine, but it's easier if it's a Virtual Machine (try out something from http://virtualbox.org). To run tests, first ensure you have bundled the gems with 'gem bundle', and copy the test.yml.example file to point at a machine which can be safely used to test SSH commands. Note: add the moment, the tests assume at various points a Linux, rather than an OS X, way of doing things. Copyright (c) 2009 Sam Phillips. See LICENSE for details.