Realized we weren't actually using the codebase config for anything anymore.
AFAIK most maintainers aren't much a fan of configurator and we've talked in the past about replacing it. Getting rid of it now seems like an auspicious plan so we're actually motivated to replace it with something better if/when we need to.
For codebase-level config it seems like we've been leaning towards just putting things in SQLite, but could also just use TOML, YAML or JSON or w/e
As a bonus, getting rid of this removes a file-watch thread and means we don't need to parse the config on every startup.
Overview
Realized we weren't actually using the codebase config for anything anymore.
AFAIK most maintainers aren't much a fan of configurator and we've talked in the past about replacing it. Getting rid of it now seems like an auspicious plan so we're actually motivated to replace it with something better if/when we need to.
For codebase-level config it seems like we've been leaning towards just putting things in SQLite, but could also just use TOML, YAML or JSON or w/e
As a bonus, getting rid of this removes a file-watch thread and means we don't need to parse the config on every startup.
Implementation notes
Wipe out configurator entirely.