On Feb 16, 2007, at 11:29 PM, Richard Harding wrote:
>
> Christopher Arndt wrote:
>> Richard Harding schrieb:
>>
>>> The next step is to see if I can tell each application in
>>> supervisord to
>>> open/start in a specific working directory so that I don't have
>>> to hard
>>> code paths in prod.cfg.
>>>
>>
>> That's easy: I just create a little wrapper shell script in my
>> project
>> directory called "run":
>>
>> ---- 8< ----
>> #!/bin/bash
>>
>> cd "${0%/*}"
>> exec ./start-myapp.py ${1:-prod.cfg}
>> ---- >8 ----
>>
>> and then I can say in supervisord.conf:
>>
>> command=/home/dev/apps/MyApp/run
>>
>> or
>>
>> command=/home/dev/apps/MyApp/run dev.cfg
>>
>>
> Thanks for the bit of bash. That's working great. I'm going to work
> on a
> wiki/blog post about the stuff required to get this to run. Can I use
> that as a recommended method of running the app?
I's usually not a good idea to run daemons with a working directory
other than "/" because that would prevent unmounting the filesystem
the app is rooted at during server mainteinance.
Alberto
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
