Using a JSON file is...fine, but if we want to potentially use KC across multiple Slack instances, we should probably have a more robust backend for it than a single JSON file. We could start with SQLite to get the ball rolling and could inform our decision to use something else (e.g. Postgres) when we possibly containerize the lot of it.
Using a JSON file is...fine, but if we want to potentially use KC across multiple Slack instances, we should probably have a more robust backend for it than a single JSON file. We could start with SQLite to get the ball rolling and could inform our decision to use something else (e.g. Postgres) when we possibly containerize the lot of it.