git.iko.soy/heroku-buildpack-stack
on master help sign in
rm unnecessary absolute pathing to executable; explain how to find executable name
commit66f0c2bc8532bd2402ef83f999bc363c1a72f9f8 authorBrad Chase <brad@these8bits.com> dateSun 25 Jun 2017, 15:06 (9 years ago) parent2bdfb3c
2 files changed+7−3
compare with master
unifiedsplit
Procfile.example+1−1 README.md+6−2
Procfile.example+1−1
@@ -1 +1 @@
1−web: /app/.local/bin/YOURAPPNAME-exe
1+web: YOURAPPNAME-exe # $ cat *.cabal | grep executable
README.md+6−2
@@ -12,9 +12,13 @@ Set this buildpack on an existing app:
1212
1313 $ heroku buildpacks:set https://github.com/mfine/heroku-buildpack-stack
1414
15−Then, assuming your application is [binding to `$PORT`](https://devcenter.heroku.com/articles/dynos#web-dynos), run your app by [creating a `Procfile`](https://devcenter.heroku.com/articles/procfile) at your project root:
15+Binary executables are placed in `/app/.local/bin/` after compilation, a directory which Heroku includes in your `$PATH`, so assuming that your application is [binding to `$PORT`](https://devcenter.heroku.com/articles/dynos#web-dynos), you can serve your app by [creating a `Procfile`](https://devcenter.heroku.com/articles/procfile) at your project root that defines a `web` process type for the `executable` defined in your `.cabal` file:
16+
17+ $ cat *.cabal | grep executable
18+ executable YOURAPPNAME-exe
19+
20+ $ echo "web: YOURAPPNAME-exe" >> Procfile
1621
17− $ echo "web: /app/.local/bin/YOURAPPNAME-exe" >> Procfile
1822
1923### Templating stack.yaml
2024