These instructions solved my issue, but I'm not sure if this is the best way to address the core issue. Guard::Rake could alternatively detect changes to the Rakefile and (optionally?) reload it - or perhaps this functionality could be a future addition.
These instructions solved my issue, but I'm not sure if this is the best way to address the core issue. Guard::Rake could alternatively detect changes to the Rakefile and (optionally?) reload it - or perhaps this functionality could be a future addition.