Is log_config being honored?

[mozart27]

I am having trouble getting log_config to be honored. When I specify log_config like this:

    "watch:serve": "export log_config=./local.config.prod && ts-node-dev --respawn ./src/server.ts",

ulog does not pick up the filename from the log_config env var.

I am likely using this improperly and the example in your documentation does not provide a practical example (it shows log_config=./my.log.config). It is possible I am missing something in the docs though.

I have also tried this:

ulog.set('log_config', './log.config.dev');

Is there something I would need to do w/r to ulog to get it to reload configs from file?

Any help would be greatly appreciated.

[Download]

I have to admit this feature has not been tested very extensively yet.
Did you try with an absolute file path?

I quickly took a look at the code that reads the config and it seems maybe there is a bug there:

module.exports = function(ulog, callback) {
  var settings = grab(ulog, 'settings', {})
  var log_config = ulog.get('log_config') || 'log.config'
  ..

https://github.com/Download/ulog/blob/master/mods/config/read.js#L11

It seems I messed up here. I should have written:

  var log_config = ulog.get('config') || 'log.config'

When using ulog.get we should use the setting name (config) and not the config alias (log_config) but alas I think I messed up here.

If you go into node_modules/ulog/mods/config and open read.js you can hack this line and change it. Does that fix it for you? If so, we can quickly fix this. I am swamped in work atm so it may take some time for me to try this myself but eventually I will fix this. But maybe you can help?

@mozart27