The compiler/server component of Flowerbox
Go to file
John Bintz 4b6c09c7bc so that almost preps the project for being merged back into the flowerbox gem proper... 2012-03-16 11:15:43 -04:00
config initial commit, starting work on features 2012-01-19 15:59:05 -05:00
features also handle jst and css base files 2012-02-08 12:41:18 -05:00
lib so that almost preps the project for being merged back into the flowerbox gem proper... 2012-03-16 11:15:43 -04:00
spec deal with a coffeescript file 2012-01-30 11:34:57 -05:00
.gitignore deal with a coffeescript file 2012-01-30 11:34:57 -05:00
Gemfile initial commit, starting work on features 2012-01-19 15:59:05 -05:00
Guardfile also handle jst and css base files 2012-02-08 12:41:18 -05:00
LICENSE initial commit, starting work on features 2012-01-19 15:59:05 -05:00
README.md initial commit, starting work on features 2012-01-19 15:59:05 -05:00
Rakefile simple sprockets work 2012-01-23 11:58:20 -05:00
flowerbox-delivery.gemspec more hacking 2012-03-14 13:07:28 -04:00

README.md

Flowerbox Delivery

Fresh cut code testing flowers, delivered straight to your door!

This component of Flowerbox uses Sprockets to compile your test suite's code into a nice package, then delivers it to a runner in two ways:

  • Straight on the filesystem, the absolute fastest way to run your tests
  • Through a Rack server, so you can teest things that need a real HTTP url, like history and WebWorkers

Installation

Add this line to your application's Gemfile:

gem 'flowerbox-delivery'

And then execute:

$ bundle

Or install it yourself as:

$ gem install flowerbox-delivery

Usage

TODO: Write usage instructions here

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request