ilyakooo0/heroku-buildpack-stack
1
0
Fork 0
mirror of https://github.com/ilyakooo0/heroku-buildpack-stack.git synced 2024-11-22 01:14:42 +03:00
Code Issues Projects Releases Wiki Activity

rm unnecessary absolute pathing to executable; explain how to find executable name

Browse Source
This commit is contained in:
Brad Chase 2017-06-25 15:06:06 -04:00
parent 2bdfb3c8e4
commit 66f0c2bc85
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Procfile.example
View File

@ -1 +1 @@
web: /app/.local/bin/YOURAPPNAME-exe
web: YOURAPPNAME-exe # $ cat *.cabal | grep executable

8
README.md
View File

@ -12,9 +12,13 @@ Set this buildpack on an existing app:
$ heroku buildpacks:set https://github.com/mfine/heroku-buildpack-stack
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:
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:
$ cat *.cabal | grep executable
executable YOURAPPNAME-exe
$ echo "web: YOURAPPNAME-exe" >> Procfile
$ echo "web: /app/.local/bin/YOURAPPNAME-exe" >> Procfile
### Templating stack.yaml