--- I just discovered the LiveReload gem, and wanted to use foreman to help me set up my development environments. I didnt want to check in my custom development Procfiles, so I needed to alter the behaviour of: > [The Procfiles] containing directory will be assumed to be the root directory of the application. Ive set up some shared `Procfiles` for development, such as `Rails3Dev`, `Rails31Dev`, `JekyllDev`, etc. Then I set up a bash alias for each of these Procfiles, such as: ```bash alias rd31="foreman start -d . -f ~/dev/procfiles/Rails31Dev" ``` The only thing missing was the `-d` flag. My `Rails31Dev` file looks like this: ```yaml compass: compass watch --sass-dir app/assets/stylesheets --css-dir public/assets livereload: livereload passenger: passenger start ``` Thanks! Conflicts: lib/foreman/cli.rb
* File.join won't expand `~` into `ENV['HOME']` (http://ruby-doc.org/core-1.9.3/File.html#method-c-expand_path) * The FakeFS File.exists? implementation calls FileSystem#find (https://github.com/defunkt/fakefs/blob/master/lib/fakefs/file_system.rb#L22-33) containing a call to FileSystem#normalize_path which expands the path variable passed in (https://github.com/defunkt/fakefs/blob/master/lib/fakefs/file_system.rb#L91-98) * The file system mocking library sets up a false expectation that `~` will be expanded in the #export_template method and consequently the production code can't use the template directory * To guard against future regressions such as fixes/updates to FakeFS or using an alternate file system mocking library, the specs were updated to explicitly set `ENV['HOME']`
…or exec for running commands in the foreman environment. Fix some error reporting.