Closed robingroppe closed 7 years ago
The reason we created the override_config was to provide a simple config file with the most important configuration options only at a time when the configuration file was really huge. It was not meant that the admin does not need to look into the default config file anymore.
Now the configuration file is much smaller and also split in to a main file and plugin specific files. I just compared config/config.yml with templates/override_config.yml and they differ in a few lines only.
However it makes sense to add logfile: "/home/botmaster/logs/bot1.log"
to the override_config.yml, tank you :)
I don't consider this as a bug but this entry will be there in 0.10.2. Until then one needs to add it himself.
@dafoxia: Do we still want that override config file? Note that we also override some plugin settings there.
For now I added this to the override_config.yml:
# IMPORTANT: Please read http://mumble-ruby-pluginbot.rtfd.io/en/master/explain_the_config.html#default-configuration-and-override-configuration to understand how this override configuration works.
@robingroppe Do you think that is better now?
There was also an error with multiple bots running with the manage.sh script from 0.10.1. It was rewritten and improved in 0.10.2.
Fixed :)
I had some trouble with a setup of three bots. Only the second and third one were working properly.
As it turns out the logfile is hardcoded in the
mumble-ruby-pluginbot/config/config.yml
and never overwritten in thesrc/botX_conf.yml
.It seems that it causes strange things when all bots try to write in the bot1.log ;).
Please add
logfile: "/home/botmaster/logs/bot1.log"
to themumble-ruby-pluginbot/templates/override_config.yml