Shannon, On Wednesday 07 March 2007 22:22, Shannon -jj Behrens wrote: > The .ini file is site-specific. Just like Debian admins have to > modify Apache configs, they also have to create and modify .ini's.
Okay, I think I understood that now. Seems like Paste has much more functionality that is not covered in the default development.ini. > As far as running a daemon, I use "runit". What about "paster serve --daemon production.ini start"? Are you scared that this daemon might crash without noticing and thus use "runit"? I also read about daemontools. > I'm not sure this is helpful to you, but here is a log of my > activities on my most recent server build: Yes, that's interesting indeed. > Setup explorer (the name of my app): > mkdir /home/explorer On Debian I would install the package into the place where other Python modules go. Example: /usr/share/pycentral/dnsdhcp/site-packages/myproject > mkdir /var/tmp/explorer I intend to use /var/cache/pylons-myproject for it. But, yes, it should be under /var. > chown www-data:www-data /var/tmp/explorer I thought about using another user than "www-data" because that's already used by Apache. But after all we are talking about web services here. > cd /home/explorer > paster make-config explorer explorer-production.ini Which unfortunately doesn't work at the moment. But a production.ini doesn't look very complicated so I think I can invent one. Thanks for sharing. Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
