Just peeked at your code, and it seems to indeed compile everything at
startup. I'm not quite remembering all of the details, but I remember that
Chestnut got it right: on Heroku, you can set things up so that an uberjar
is created on git push and then started with java -jar on startup, which is
usually much faster. See for example:

https://github.com/plexus/chestnut/blob/master/src/leiningen/new/chestnut/Procfile

I *think* it was enough to declare an :uberjar-name entry in the
prpject.clj to trigger that behaviour on Heroku, but I am not quite sure.
You'll have to experiment a bit (or hope someone else can answer more
definitely).

On Monday, 27 July 2015, Gary Verhaegen <[email protected]> wrote:

> the error message also sugget that your process may not have started
> quickly enough. How do you deploy on heroku? Do you have a Procfile? What
> does it say? Do you prepackage on push, or recompile everything on startup?
>
> On Monday, 27 July 2015, Divyansh Prakash <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
>> Hi!
>>
>> I had written a poetry generator <http://yushing.herokuapp.com/>
>> sometime back and wanted to convert it into a Twitter bot.
>> I followed this tutorial <https://howistart.org/posts/clojure/1> to do
>> so. You can find my code here <https://github.com/divs1210/yushing-bot>.
>>
>> The bot's working fine from my local machine, but sporadically crashes on
>> Heroku with the following message:
>>
>>> 2015-07-27T10:23:06.574908+00:00 heroku[web.1]: Error R10 (Boot timeout)
>>> -> Web process failed to bind to $PORT within 60 seconds of launch
>>> 2015-07-27T10:23:06.574908+00:00 heroku[web.1]: Stopping process with
>>> SIGKILL
>>> 2015-07-27T10:23:07.550373+00:00 heroku[web.1]: Process exited with
>>> status 137
>>> 2015-07-27T10:23:07.561392+00:00 heroku[web.1]: State changed from
>>> starting to crashed
>>
>>
>>  Some answers on SO suggest that this is because Heroku already provides
>> a port to bind to and I might be trying to bind to some other port, but
>> this is not the case.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to [email protected]
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to