Almost, except I need to be able to define this independently for custom purposes. For example:
modparam("permissions", "db_url", "postgres:// @cfg_get.db.user:@cfg_get.db.password@@cfg_get.db.host/ @cfg_get.user.dbname")
-- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892
On Apr 9, 2010, at 4:44 AM, marius zbihlei marius.zbihlei@1and1.ro wrote:
Alex Balashov wrote:
Allow cfg_get parameters to be used as modparams, too, so I can define one set of global database properties and pass them as db_urls to every module that uses one and also to 'sqlops' as an 'sqlcon', and similar things.
Hello Alex,
I don't know if this is exactly your wish but if you specify cfg_get parameters as module parameters than you get the desired effect.
For example in carrierroute module (master branch), in the definition of modules parameters I have ... {"use_domain", INT_PARAM, &default_carrierroute_cfg.use_domain } ...
You can set/get use_domain via the cfg framework at runtime(using sercmd), or initially via modparam...
This is what you wanted ?
Marius