airbyte/dbis in this case unused, and can therefore be removed or de-activated from the
docker-compose.ymlfile). It's not a good practice to deploy mission-critical databases on Docker or Kubernetes. Using a dedicated instance will provide more reliability to your Airbyte deployment. Moreover, using a Cloud-managed Postgres instance (such as AWS RDS our GCP Cloud SQL), you will benefit from automatic backup and fine-grained sizing. You can start with a pretty small instance, but according to your Airbyte usage, the job database might grow and require more storage if you are not truncating the job history.
.envfile (used by the docker-compose command afterward):
DATABASE_URLto include the correct host, port, and database. If you need to provide extra arguments to the JDBC driver (for example, to handle SSL) you should add it here as well:
airbyte-dbPostgres database, if a developer wants to access the data that tracks jobs, they can do so with the following instructions.
.envfile that is used to run Airbyte. By default, the values are: