> Very nice setup is to keep the whole project in one file, for example > .ini. > uWSGI has its own section and I can manage the rest. > The problem is that any change in the file .ini effect of restarting the > application (emperor mode). > Is it possible to make only restart when something changes in the [uwsgi] > section, and if change is made ââin another section reboot should not > be executed. Unless we touch-reload .ini file ? > >
Pretty challenging, maybe it is best to put this logic in the vassals to reuse in other areas too. I mean: - emperor sees the touch in the vassal's config file - as emperor has been set in "smart" mode, it sends the "smart-reload" message to the vassal (instead of the normal "reload") - the vassal's master receives the "smart-reload" request - the vassal's reopen the configfile and creates a new exported_options list (the internal structure used by uWSGI) - the vassal compares the two list and if they are different it goes on with the reload. Otherwise it ignores the request. The same could be applied for normal reloads without emperor and without changing too much code. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
