Postgres - Features, integrations, alternatives & more
What it does
How it works
The Postgres service runs as a separate container but in the same network as the action to which is attached. This includes other services attached to the action. Buddy runs main action commands only once the service is fully initialized. There is no need to check Postgres availability on your own. The service is terminated once the action is completed. The service is cacheable it means data generated and stored by the service can be set persistent between action executions.
How to connect to the service from the action, an cqlsh example:
export PGPASSWORD='root'; psql -h 'postgres' -U 'root' -d 'mydb' -c 'command'
"postgres" is a default hostname for the service (settable in the service options)
Postgres service features:
- Version setting including latest tag (the versions are pulled from Docker Hub)
- Hostname setting for connecting between action and other services
- The port is fixed (5432) and can’t be changed
- You can set a name of the database that will be created on the container setup
- You can populate your database with repository SQL dump (support sql and sql.gz)
- Setting Container CMD which will overwrite default Cassandra start command. It allows to use advances settings provided by the Cassandra Docker image.
- Cache database between executions flag. Use this option to speed up your exactions if no fresh or clean Cassandra instance is required.