On 2011-04-18 16:36:28 -0700, Daniel Holth said:
On Apr 18, 2011, at 6:09 PM, Alice Bevan–McGregor wrote:
I've already defined that. RTFM or many ML messages about logging.
Please remain friendly and patient.
That depends on how you define the F in RTFM. In this instance, I
meant "read t
On Apr 18, 2011, at 6:09 PM, Alice Bevan–McGregor wrote:
> On 2011-04-18 14:11:21 -0700, Daniel Holth said:
>
>> If you want the format to specify cron jobs and services and non-wsgi
>> servers, why not go the whole way and use the Linux filesystem hierarchy
>> standard. The entry point is an
> If you want the format to specify cron jobs and services and non-wsgi
> > servers, why not go the whole way and use the Linux filesystem
> > hierarchy standard. The entry point is an executable called `init`,
> > configuration goes in /etc/, cron jobs go in /etc/cron.d etc. This
> > should b
On 2011-04-18 14:11:21 -0700, Daniel Holth said:
The file format discussion seems utterly pointless.
That's a pity.
If you want the format to specify cron jobs and services and non-wsgi
servers, why not go the whole way and use the Linux filesystem
hierarchy standard. The entry point is an
The file format discussion seems utterly pointless. Roberto de Ioris's uWSGI
seems to make do with every file format. Would it be more useful to talk
about what the deserialized configuration looks like in Python?
If you want the format to specify cron jobs and services and non-wsgi
servers, wh
