Indeed. It sounds like you should not use the deployment tool. As far as I know Yesod still works without it.<div><br></div><div><br></div><div>Aristid</div><div><br><br>Am Freitag, 4. Mai 2012 schrieb Vagif Verdi :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Why not ? It's an intranet app, few users, it does what we need. Its simple to deploy (one app instead of several separate apps). Much simpler infrastructure. Now i understand those awesome startups who deploy to Heroku of AWS or what have you in hopes to build next Facebook. Sure, go wild, nosql, thousands workers complex infrastructure.<br>
<br>But why would i overcomplicate my small intranet app, just because your deployment tool is not flexible enough ? It would be simpler for me just not to use your deployment tool :)<br><br><br>On Friday, May 4, 2012 10:10:32 AM UTC-7, Lyndon wrote:<blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't think that it's generally considered a good idea to have
<br>long-running processes occurring in-app. I know that on Heroku there
<br>are 'workers' that you can provision to take care of such tasks. These
<br>could even run as their own apps that connect to the same resources
<br>for queueing, etc, in order to reuse the deployment interfaces and
<br>infrastructure.
<br>
<br>Deciding to hold off on a restart of an application due to what would
<br>usually be asynchronous operations seems a bit fishy.
<br>
<br>On Sat, May 5, 2012 at 12:32 AM, Vagif Verdi wrote:
<br>> I have an intranet app that has a couple of long running operations. Say
<br>> batch print 50 pdf files to printer. Or submit 10,000 invoices to ADP Tax
<br>> server (end of month).
<br>>
<br>> Maybe killing the app server should be optional.
<br>>
<br>>
<br>>
<br>> On Friday, May 4, 2012 7:55:21 AM UTC-7, Michael Snoyman wrote:
<br>>>
<br>>> send the TERM signal to the old app,
<br></blockquote></blockquote></div><span></span>