Hi All,
I am comming up against a strange issue where the uwsgi emperor see's
two different configuration files, albeit with the same filename, as the
same instance.
I have two scan directories configured:
[1] /path/to/prod
[2] /path/to/dev
In the prod directory I hav a "production" skeleton/template file which
I symlink the configuration file to. Within the skeleton I use the %n
directive to setup application paths, virtualenv paths and log file paths.
In the dev directory, I have a similar "development" skeleteon/template
file which I symlink the configuration file to.
In the prod path, if I symlink myapp.ini, the emperor starts up an
instance and its starts up properly.
If, in the dev path, I symlink myapp.ini to the dev skeleton, it
restarts my prod instance defined previously.
Is this the expected behaviour? Is it possible to run two seperate
instances under emperor mode, with the same configuration filename?
I am running uwsgi v2.0.11.2
Any pointers would be greatly appreciated.
Thanks
--
Know a business that could benefit from Blueface?
Refer a customer on <http://goo.gl/forms/2JqS83fWeA> and you'll both get a
month free of your call plan.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
