Alex Morega ha scritto:
> On 17 Mar 2010, at 13:47, Manlio Perillo wrote:
> [...]
>>> =
>>> [daemon]
>>> factory = egg:PasteScript#wsgiutils
>>> host = 127.0.0.1
>>> port = 8000
>>> app = my_site
>>>
>>> [...]
>>>
>> If you want this, isn't it more simple and generic to use
On 17 Mar 2010, at 13:47, Manlio Perillo wrote:
> Alex Morega ha scritto:
>> On 17 Mar 2010, at 0:24, Manlio Perillo wrote:
>>
>>> Alex Morega ha scritto:
Hello,
This is not really a WSGI question, it's more into general configuration,
but I don't know of a better place to
Alex Morega ha scritto:
> On 17 Mar 2010, at 0:24, Manlio Perillo wrote:
>
>> Alex Morega ha scritto:
>>> Hello,
>>>
>>> This is not really a WSGI question, it's more into general configuration,
>>> but I don't know of a better place to ask it.
>>>
> [...]
>> I use YAML with custom constructors:
On 17 Mar 2010, at 0:24, Manlio Perillo wrote:
> Alex Morega ha scritto:
>> Hello,
>>
>> This is not really a WSGI question, it's more into general configuration,
>> but I don't know of a better place to ask it.
>>
>> Paster config files allow you to hook up WSGI applications, middleware, and
Alex Morega ha scritto:
> Hello,
>
> This is not really a WSGI question, it's more into general configuration, but
> I don't know of a better place to ask it.
>
> Paster config files allow you to hook up WSGI applications, middleware, and a
> server, plus some (undocumented?) magic configuratio
WHIFF has a concept of configurable resources
for application groups, if you care to take a look.
concept:
http://whiffdoc.appspot.com/docs/W1000_1000.resources
deployment API:
http://whiffdoc.appspot.com/docs/W1200_1000.DirectoryConfig
access API:
http://whiffdoc.appspot.com/docs/W1200_13
