Closed jejacks0n closed 9 years ago
I'm not sure what the best approach here is, but I've used this setup before and it provides some useful tooling that is otherwise still kind of a shit show with grunt and friends. Coffeescript, sass, slim (or haml etc.), and rake tasks to build javascripts etc. This takes me about 2 minutes to setup, and I kinda wrote teaspoon to allow for these simplistic setups that I personally enjoy.
I'm wondering if we just continue on if unable to find the standard rails environment, and let it fail over if rails is still undefined after locating/loading the teaspoon env?
For the record, I view this a little bit like a more familiar middleman development pipeline.
I'm using 0.9 in the interim -- I couldn't find a simple/good fix.
I have a micro rails application -- with my development application defined in a simple
config.ru
file.I then put a
teaspoon_env.rb
in the spec directory, as per the standard -- and require rails in it:This simple setup no longer works because internally to teaspoon, it's making assumptions about how rails is setup in pathing and file structures. This seems like a negative thing to tie teaspoon to, and makes it feel more coupled to rails than desired.