Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Document COMANAGE_REGISTRY_NO_DATABASE_CONFIG in cron README.md
Document the use of the COMANAGE_REGISTRY_NO_DATABASE_CONFIG environment
variable in the README.md file for the cron image.
skoranda committed Mar 23, 2020
1 parent 4450c1f commit 6b015cc
Showing 1 changed file with 17 additions and 1 deletion.
18 changes: 17 additions & 1 deletion comanage-registry-cron/README.md
@@ -80,7 +80,20 @@ See the [list of environment variables common to all images](../docs/comanage-re
including this image. Since this image does not run a webserver many of the environment variables will
be ignored by containers instantiated from this image.

If you do not use the same volume that is used with COmanage Registry be sure
If you use the same volume that is used with COmanage Registry then you should
set the environment variable

```
COMANAGE_REGISTRY_NO_DATABASE_CONFIG
```

to any value so that the cron container does not attempt to also create
the database configuration file along with the COmanage Registry container.
Failure to do so may lead to a race condition where the cron container
writes an incorrect database configuration file because it does not
have access to the same details as the full COmanage Registry container.

If you do *not* use the same volume that is used with COmanage Registry be sure
to set the environment variables

* `COMANAGE_REGISTRY_DATASOURCE`
@@ -89,6 +102,9 @@ to set the environment variables
* `COMANAGE_REGISTRY_DATABASE_USER`
* `COMANAGE_REGISTRY_DATABASE_USER_PASSWORD`

so that the container is able to write its own database configuration file
and connect to the database.

See also the next section for details on how to specify the location of
the crontab file.

0 comments on commit 6b015cc

Please sign in to comment.