This page describes how to setup Bytebase in production environment.
You can use Caddy or Nginx. Check out the configuration example.
See Configure External PostgreSQL.
Access telemetry at /metrics
(e.g. https://demo.bytebase.com/metrics).
You can only run a single Bytebase instance at any point it time. In another word, you can scale-up the instance but not scale-out the instance to multiple replicas.
Restarting the Bytebase instance usually takes under 10 seconds. To minimize the downtime, you should store the metadata in an external PostgreSQL and make sure the PostgreSQL instance is highly available.
If Bytebase is configured to store either metadata or the backups on the local disk, then you must use Persistent Volume. Local disk cannot persist state and can also cause frequent pod eviction due to disk pressure during backup.
If you self-host Bytebase in the cloud provider, below is the recommended stack.
This page describes how to setup Bytebase in production environment.
You can use Caddy or Nginx. Check out the configuration example.
See Configure External PostgreSQL.
Access telemetry at /metrics
(e.g. https://demo.bytebase.com/metrics).
You can only run a single Bytebase instance at any point it time. In another word, you can scale-up the instance but not scale-out the instance to multiple replicas.
Restarting the Bytebase instance usually takes under 10 seconds. To minimize the downtime, you should store the metadata in an external PostgreSQL and make sure the PostgreSQL instance is highly available.
If Bytebase is configured to store either metadata or the backups on the local disk, then you must use Persistent Volume. Local disk cannot persist state and can also cause frequent pod eviction due to disk pressure during backup.
If you self-host Bytebase in the cloud provider, below is the recommended stack.