I'm trying to squeeze some more performance out of a cluster and an easy
fix was segmenting out all the "admin" routes/views to be conditionally
enabled. (This saves enough MB per process that I can run a handful more
processes. yay.)
I'm trying to figure out a good way to re-enable the "admin" routes though.
* pyramid is deployed via uwsgi , which is controlled by supervisord.
* uwsgi is invoked using the `--ini-paste--logged` argument, which which
points to the "production.ini"
I was thinking that the easiest way to enable/disable the admin routes
would be to just set an environment variable in supervisord and just look
for it in the app. something like...
[program:myapp-main]
...
environment = MYAPP_DISABLE_ADMIN=1
command = uwsgi --ini-paste-logged production.ini
[program:myapp-admin]
...
command = uwsgi --ini-paste-logged production.ini
Does this sound like a good idea? Has anyone else done this, or used
another method?
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
