geonetwork / geonetwork/docker-geonetwork
Use geonetwork database parameters in stead of customised
- Dominant language
- Shell
- Stars
- 40
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
database configuration is injected in scripts from docker only environment variables in a deploy script
https://github.com/geonetwork/docker-geonetwork/blob/9fcf08514e1cbcd6b4f48a1d6acfac9fd23afa2d/3.10.0/postgres/docker-entrypoint.sh#L45
However geonetwork already has a mechanism to inject environment parameters into the application, to prevent extra (contradicting) documentation, i recommend to use the default geonetwork injection mechanism
```
docker run -e jdbc.database=example...
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with 3.10.0/postgres/docker-entrypoint.sh around line 45 and compare its database environment handling with the GeoNetwork injection mechanism. Use the documented `docker run -e jdbc.database=example...` form as the reference, and finish when the custom deployment injection is replaced without contradictory configuration paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100