We’ve had support for both config.json
and the new jibri.conf
for a while now, and I think I’ll be looking to officially deprecate the old config file soon. This is partly motivated by a big Jibri refactoring I did recently (PR here) where I just left out support for the old config.json. This won’t happen in the next couple weeks, but I hope to get that Jibri refactor merged sometime early next year, so wanted to put out a first warning.
When that Jibri PR is merged Jibri will move to version 9, but the debian package will still be the same, so upgrading would take this new version and break deployments who were still relying on the old config file. (I can probably at least check for the program argument being passed and log a bit warning if --config
was still passed in).
Any thoughts?