> Hello everybody, > > I'm currently trying to build an hyperscalable service based on a uWSGI > Cluster. > For now, my own Python application is running fine on our Q/A servers, but > I was wondering something. > > I've set my uWSGI nodes with a configuration file which is well filled and > as most of our needed generic settings. > > But, this nodes will be availables for our developers teams, and they will > directly push their own application with her yaml config file on a > personnal home directory. > > My problem here is to know if ever I set a skeleton files which a bunch of > specific properties like uid=blabla and something else, will those > settings > overrides the settings of the developers yaml config file, or not? > > In fact I just want to start my nodes with a default config file for the > uWSGI container and then use a skeleton to overrides each developers > personnal config file to avoid anykind of privileges escalation or other > shared ressources problems because I know that some of them will want to > override the limits fixed by the uWSGI Config. > > If I'm missing something or if I do not explain myself correctly just let > me know it :D > > Kind regards, > Gaël. >
You need something like that: [uwsgi] ; start with default options default_option1 = foo default_option2 = bar ; include developer custom options yaml = path_to_developer_yaml.yml ; override developer options uid = test001 gid = test002 ; reload the server when the user changes its config touch-reload = %(yaml) Related documentation: http://projects.unbit.it/uwsgi/wiki/ParsingOrder You may be interested in this new approach (requires 1.9): https://github.com/unbit/uwsgi/issues/171 -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
