Describe the feature
Add a supported production-oriented Docker Compose example for deploying Kival.
The 0.1.0 release intentionally omitted the previous production Compose setup because it had not been sufficiently validated. The removed etc/ setup is attached to this issue as a starting point.
The new example should provide a realistic single-instance deployment with PostgreSQL, persistent Kival data, production configuration, and useful observability. It should be tested and documented well enough that Kival can reasonably present it as a production reference deployment.
Additional context
The attached setup includes the previous Docker Compose configuration together with Prometheus, Grafana, Loki, Alloy, and the Kival Grafana dashboard.
Treat it as reference material rather than something that should simply be restored unchanged. Re-evaluate and simplify its assumptions against the current Kival release where appropriate.
The development Compose setup should remain separate. Multi-instance deployment and cloud object storage are tracked independently.
etc.zip
Describe the feature
Add a supported production-oriented Docker Compose example for deploying Kival.
The 0.1.0 release intentionally omitted the previous production Compose setup because it had not been sufficiently validated. The removed etc/ setup is attached to this issue as a starting point.
The new example should provide a realistic single-instance deployment with PostgreSQL, persistent Kival data, production configuration, and useful observability. It should be tested and documented well enough that Kival can reasonably present it as a production reference deployment.
Additional context
The attached setup includes the previous Docker Compose configuration together with Prometheus, Grafana, Loki, Alloy, and the Kival Grafana dashboard.
Treat it as reference material rather than something that should simply be restored unchanged. Re-evaluate and simplify its assumptions against the current Kival release where appropriate.
The development Compose setup should remain separate. Multi-instance deployment and cloud object storage are tracked independently.
etc.zip