djinn-curator is the component that handles cleaning up of old artifacts that exceed a given limit. Every minute this will trigger and remove the oldest artifacts that exceed the configured limit of the curator.
Detailed below are the software dependencies that the curator needs in order to start and run,
|PostgreSQL||Primary data store for the curator.|
Provides connection information to the PostgreSQL database.
The address of the PostgreSQL server to connect to.
The name of the database to use.
The name of the database user.
The password of the database user.
TLS configuration for connecting via TLS.
Path to the CA root to use.
Path to the certificate to use.
Path to the key to use.
Providers connection information to the Redis database.
The address of the Redis server to connect to.
The password used if the Redis server is password protected.
The location where the driver images are stored. The
The type of store to use, must be
The location of the store.
To run the curator simply invoke the
djinn-curator binary. There are only two flags that can be given to the
-config - This specifies the configuration file to use, by default this will be
-limit - This specifies the limit in bytes to use for clearing up artifacts, by default this will be set to
dist directory contains files for running the Djinn Curator as a daemon on Linux systems that use systemd and SysVinit for daemon management. Use whichever suits your needs, and modify accordingly.
If deploying to a Linux system that uses systemd, then be sure to run
systemctl daemon-reload upon placement of the service file.