This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-21
Channels
- # beginners (82)
- # bitcoin (1)
- # boot (38)
- # cider (6)
- # cljs-dev (13)
- # cljsrn (5)
- # clojure (320)
- # clojure-italy (22)
- # clojure-losangeles (6)
- # clojure-russia (55)
- # clojure-spec (25)
- # clojure-uk (48)
- # clojurescript (64)
- # component (16)
- # core-async (6)
- # cursive (54)
- # data-science (2)
- # datascript (2)
- # datomic (8)
- # docker (1)
- # ethereum (1)
- # fulcro (1)
- # garden (1)
- # graphql (16)
- # heroku (6)
- # hoplon (12)
- # jobs (4)
- # juxt (1)
- # leiningen (9)
- # off-topic (39)
- # om (13)
- # om-next (2)
- # onyx (9)
- # pedestal (2)
- # portkey (12)
- # re-frame (25)
- # reagent (6)
- # ring-swagger (4)
- # schema (1)
- # shadow-cljs (10)
- # spacemacs (11)
- # testing (19)
- # uncomplicate (1)
- # unrepl (6)
- # vim (21)
- # yada (3)
The only tutorial I know is the one on heroku.https://devcenter.heroku.com/articles/getting-started-with-clojure#introduction
That said... I am having trouble with a deployment, too.
The app compiles cleanly both locally and on heroku (clj + cljs without any warnings or errors).
However, heroku logs
shows
2017-09-21T17:27:04.939205+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2017-09-21T17:27:04.939205+00:00 heroku[web.1]: Stopping process with SIGKILL
2017-09-21T17:27:05.433004+00:00 heroku[web.1]: Process exited with status 137
2017-09-21T17:27:05.449591+00:00 heroku[web.1]: State changed from starting to crashed
If I run the jar locally with the same command that is in the Procfile it works.
How can I debug what is wrong on the heroku instance?