Pylons and Paste are meant to run in a wide variety of OSs. This is the type of stuff where it makes sense to take advantage of what your particular OS provides. For me on Ubuntu, that was runit.
My $0.02, -jj On 5/25/07, voltron <[EMAIL PROTECTED]> wrote: > What actually is recommended by the Pylons gurus? The monitor and > reload functions are there for a purpose, are they to be used in > production? > > Thanks > > On May 25, 7:49 am, "Max Ischenko" <[EMAIL PROTECTED]> wrote: > > On 5/25/07, Mike Orr <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > On 5/22/07, Ian Bicking <[EMAIL PROTECTED]> wrote: > > > > > My other question is, paster has a --monitor-restart option to restart > > > > > the server if it dies. But the Pylons Cookbook has recipes for > > > > > daemontools and supervisor2. Are these better than paster's monitor > > > > > for some reason, or are they all interchangeable? > > > > > > They all work the same basic way. paster's is simpler, obviously, since > > > > it's just one option. But it hasn't been tested a whole lot, so I > > > > dunno. Also it probably has more overhead than daemontools, though I > > > > don't know if it really is significant. > > > > > I looked through supervisor2 and am really impressed with its > > > features, but I couldn't get it to run my application and it wouldn't > > > say why not. According to the docs, this happens frequently for a few > > > reasons that didn't seem to apply. I wish it would take more care to > > > write a specific error message. > > > > > I suspect the problem was needing to set the PATH and PYTHONPATH to > > > match my workingenv. I used the beta version of supervisor2 which > > > lets you set per-application environment variables. But the app just > > > wouldn't start for no reason so I don't know if they were set. I > > > tried launching "printenv" but it also quit silently -- and without > > > printing the environment to the log file. > > > > I had problems getting started with supervisor2 but logs were of great help. > > It can log everything the application-under-run sends to stdout/stderr. > > > > The usual suspects are permissions (are you sure you're starting from > > correct user? that user has permissions to open logfile your app using?) and > > paths. > > > > Max. > > > > > -- http://jjinux.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
