I wasn't asking for a suggestion, I use a very similar setup myself currently as a matter of fact, server specifics abstracted into includes, simple script to select the right abstraction all under source control.
Another impetus for wanting to load config from HTTP is that you could serve dynamic config from a web app, i.e. customer specific configs for dedicated proxies, things which the mooted 5.0 runtime reloading could really take advantage of... -----Original Message----- From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel Tryba Sent: 02 March 2016 17:38 To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 5.0 - HTTP loading of config files On Wed, Mar 02, 2016 at 05:10:15PM +0000, Tim Chubb wrote: > As a suggestion for 5.0 being able to load config files from a URL, > with any includes being taken relative to the URL would be a really > handy feature. It would allow a central source for config files in a > cluster and make it a much simpler process to push out changes to > routing to all nodes. This problem has been solved by the many configuration management tools readily available. And no I can't give you a suggestion since I use my own manual way to upgrade from a central repos (a test server) that simply scps the config to the active nodes, includes load the per server specific parts from the filesystem. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
