Make it easier to debug the asset pipeline about heroku-buildpack-ruby HOT 15 CLOSED

I've never been a big fan of the way the rake task detection works. Is there a better way than using --dry-run?

from heroku-buildpack-ruby.

This is related to #9.

from heroku-buildpack-ruby.

A better way? No.
A different way? Yes.
https://gist.github.com/2922172

from heroku-buildpack-ruby.

Proposal:

• Using something akin to the gist provided, provide better error messaging about why the pipeline failed.
• Run pipeline in a limited environment and with --trace if DEBUG_PIPELINE=1

While a completely separate issue, follow Python's lead and allow users to turn off the pipeline entirely via DISABLE_PIPELINE=1

from heroku-buildpack-ruby.

@wuputah how does python do this?

from heroku-buildpack-ruby.

:s/ @wuputah / @kennethreitz /

from heroku-buildpack-ruby.

I allow users to disable it with DISABLE_COLLECTSTATIC=1, but ideally someone should almost never need to do that.

from heroku-buildpack-ruby.

@kennethreitz what happens if collectstatic fails (and, of course, is not disabled)?

from heroku-buildpack-ruby.

I do a dry run first. If it fails, nothing happens, the user doesn't see anything about.

If the dry run passes, I run it, if it fails, i tell them the output, and point to documentation on how to debug w/ heroku run.

from heroku-buildpack-ruby.

In the latter case, does the build still succeed?

from heroku-buildpack-ruby.

Yes. I had it fail at first, but too many people have configuration issues for that to be practical.

People have crazy configurations.

from heroku-buildpack-ruby.

In the long term future, I'd like to remove this feature completely and replace it with "add this oneliner to a build hook (e.g. bin/post_compile)" instead.

But, some things have to happen for that to be a reality.

from heroku-buildpack-ruby.

Okay, to come back to what I was talking about earlier, I was principally referring to Kenneth's use of DISABLE_COLLECTSTATIC.

from heroku-buildpack-ruby.

@wuputah i don't think we should be pushing build stuff through config vars.

from heroku-buildpack-ruby.

Should be solved by #34

from heroku-buildpack-ruby.