{"comment":{"created_at":"2011-10-10T12:00:56Z","body":"Setting this in application.rb is suggested I guess?","updated_at":"2011-10-10T12:00:56Z","url":"https://api.github.com/repos/plataformatec/devise/issues/comments/2346619","id":2346619,"user":{"avatar_url":"https://secure.gravatar.com/avatar/5054ff71a967d798cd402e8f65235bf1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/avocade","id":8943,"login":"avocade"}},"action":"created","issue":{"number":1339,"created_at":"2011-09-21T07:43:57Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"I'm not sure if this has been mentioned before, and I'm not sure where to even start fixing it. \r\nWhen deploying a Rails 3.1 app to Heroku, it runs the asset compilation rake task during the deploy.\r\nHowever in an app with devise in it this compilation fails because the devise_for route helper causes the rake task to need to talk to the database, which doesn't exist yet.\r\n\r\nIs this something that can be changed on Devise's end? \r\n\r\nAny thoughts?\r\nCheers,\r\nBrad","comments":24,"title":"Devise, Heroku and the Asset Pipeline","updated_at":"2011-10-10T12:00:56Z","url":"https://api.github.com/repos/plataformatec/devise/issues/1339","id":1694835,"assignee":null,"milestone":null,"closed_at":"2011-09-25T11:07:58Z","user":{"avatar_url":"https://secure.gravatar.com/avatar/34b3e93704a811f2befad5a894e28072?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/bradleypriest","id":167215,"login":"bradleypriest"},"html_url":"https://github.com/plataformatec/devise/issues/1339","labels":[],"state":"closed"},"legacy":{"issue_id":1694835,"comment_id":2346619}}