You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grep for the string "{:phoenix," in mix.exs and do the following if Phoenix is detected
1.) use appropriate default process type (mix phoenix.server) in bin/release script if Phoenix is detected
We can expand to other frameworks later if required.
2.) compile assets before compiling app
Phoenix uses brunch. If we detect a brunch config, then we could run brunch build --production. But I would vote for requiring users to have an npm build task instead and running something like "npm run build --production". This way it's tooling independent.
3.) use mix phoenix.digest as post-compile hook (if post_compile hook is specifically mentioned in buildpack config, then that must be used instead)
4.) use a database addon in bin/release
This is assuming almost all Phoenix apps use a database.
Right now this is how I just deployed a Phoenix app:
1.) Set "postinstall" script in package.json to run "brunch build --production"
2.) Set post compile hook in buildpack config to run mix phoenix.digest
3.) Add nodejs buildpack heroku buildpacks:add --index 1 https://github.com/heroku/heroku-buildpack-nodejs
grep for the string "{:phoenix," in mix.exs and do the following if Phoenix is detected
1.) use appropriate default process type (
mix phoenix.server
) inbin/release
script if Phoenix is detectedWe can expand to other frameworks later if required.
2.) compile assets before compiling app
Phoenix uses brunch. If we detect a brunch config, then we could run
brunch build --production
. But I would vote for requiring users to have an npm build task instead and running something like "npm run build --production". This way it's tooling independent.3.) use
mix phoenix.digest
as post-compile hook (if post_compile hook is specifically mentioned in buildpack config, then that must be used instead)4.) use a database addon in
bin/release
This is assuming almost all Phoenix apps use a database.
\cc: @ericmj
The text was updated successfully, but these errors were encountered: