-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support post compile hook #31
Comments
@chrismccord won't that mean we would need node.js installed too? (https://github.com/ddollar/heroku-buildpack-multi). \cc: @ericmj |
Just an FYI that Heroku Buildpacks have changed a bit. You no longer need the multi-buildpack to specify a build pipeline. Instead, specify each buildpack individually with the following CLI:
Regarding brunch asset compilation, here's how they do it in the official Ruby/Rails buildpack. |
Should we automatically run a /cc @josevalim |
I thought the plan was to not support hooks. What changed? :) |
At work, I was working with a non-Heroku deployed app where the Curious how a post compile hook will help on Heroku since we depend on mutl-buildpack for asset compilation. |
The problem is that you might not want to compile assets on every compilation or app start so a Heroku specific compilation step is very useful.
Not sure what you are asking here, as long as the node buildpack runs before the elixir buildpack it will work. |
@ericmj I meant to ask what the use case was for the post-compile hook. I remember there was this discussion earlier in another issue and that that issue was closed. Sorry read your comment in bed and forgot to reply the other day. |
@ericmj 👍 thanks for linking. Got it now ~! |
Yaaay ~! |
For Phoenix, we would like to have a complete buildpack solution when we ship 1.0, which means we need to be able to build brunch assets after compile. I'm not sure where to start here, but @ericmj has some idea where we need to begin.
The text was updated successfully, but these errors were encountered: