Kubernetes?

[osimmasgard]

Hi!

Are there plans to enable this software to run in a Kubernetes environment so it can be centrally managed by a platform team?

Thanks!

[BorisDelange]

Hi!

Thanks for the suggestion. Yes, a backend version is something I'm considering, and it would be the natural foundation for a Kubernetes deployment.

The current app is intentionally simple: a static SPA served by GitHub Pages, with Git acting as the source of truth and contributions flowing through pull requests. That works well for the open, community-driven side of the dictionary, but it doesn't fit the "centrally managed by a platform team" use case you're describing: there's no multi-user persistence, no authentication, no API.

Here's what I'd propose:

1. FastAPI + PostgreSQL backend: handles auth, stores concept sets/projects in the database, exposes a REST API. The existing SPA would call the API instead of reading the generated data_inline.js.
2. Two-way Git sync: the public repo stays the canonical source of truth for community-validated content. A worker would periodically pull updates from the repo into the DB, and push user contributions back as pull requests. Self-hosted instances can also run fully offline if needed.
3. Docker packaging — a Dockerfile for the API (and frontend), plus a docker-compose.yml for local development. From there, a platform team should have everything needed to deploy it in their own Kubernetes environment.

What do you think? Does this match what you had in mind, and are there specific requirements from your side (authentication method, deployment constraints, must-have features) that I should keep in mind?