On Fri, May 17, 2013 at 8:12 AM, Corey Finley <finley.corey@gmail.com> wrote:
> ... it caused error during the assest precompile.
> Anyone else having/had a similar issue or found a way around it?
Seriously? Post (or gist) the error message and stack trace if you
want to have any hope of a meaningful response.
It's also good practice to include the Ruby/Rails versions as well
as versions for any gems involved.
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
http://about.me/hassanschroeder
twitter: @hassan
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yDNC5S2gduTfNw21mBsvjMACcSczTiHG-Vcewc%3DbZs38A%40mail.gmail.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment