CodeScoring.Save Installation Options¶
CodeScoring.Save supports two installation options: a SQLite-based option in k3s and a PostgreSQL-based option in Kubernetes. Both options are installed through the save Helm chart, but they target different infrastructure and operation scenarios.
The Helm repository address and Docker Registry with CodeScoring.Save images are provided by the vendor. Installation examples use the placeholders <HELM_REPOSITORY_URL> and <REGISTRY_HOST>.
Available Options¶
| Option | When to use |
|---|---|
| Hosted installation | Testing, demonstrations, small teams, and quick start without separate PostgreSQL and S3 infrastructure |
| PostgreSQL installation | Production use, scaling, and operation with external or built-in PostgreSQL and S3-compatible storage |
Before choosing an option, check installation requirements and prepare a shared values.yaml file. The main parameters are set in these sections:
app.deploymentsapp.servicesapp.envspostgresminio
When switching between SQLite and PostgreSQL, database parameters must be set not only for backend in app.envs.DATABASE_*, but also for auth in the auth container env.
In the current values.yaml, the auth container env is defined as a name/value list.