danwatford commented on pull request #246:
URL: https://github.com/apache/ofbiz-framework/pull/246#issuecomment-736700620
Hi @ieugen , I've committed some changes to select and populate a template
entityengine.xml file based property values.
This nicely side-steps those problems I was having with Groovy's XmlParser
and hopefully reduces the complexity of login in build.gradle down to ensuring
suitable default values are in place for properties.
I had envisioned these changes would be used to create docker images that
would be used with DBMS example docker-compose specifications. Similar to your
Prometheus example I would expect key directories and configuration files to be
exposed on the host's filesystem allowing for local modification.
I thought we might end up with docker-compose files similar to:
```
services:
db:
image: postgres:13
restart: always
environment:
POSTGRES_PASSWORD: lDvEFVkVyVpHuCOK9To3
OFBIZ_DB_USER: ofbizuser
OFBIZ_DB_PASSWORD: ofbizpassword
volumes:
- ./dbdumps:/opt/dbdumps
- ./docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
ofbiz:
build: ofbiz
depends_on:
- db
ports:
- 8443:8443
- 15005:5005
environment:
ORG_GRADLE_PROJECT_ofbizDbms: postgres
ORG_GRADLE_PROJECT_ofbizDbUsername: ofbizuser
ORG_GRADLE_PROJECT_ofbizDbPassword: ofbizpassword
```
There are still some things to figure out. Perhaps we should avoid
overwriting any existing entityengine.xml file if it exist, instead requiring
an explicit call to the copyEntityEngineXml task to create a file which is then
exposed by docker for editing.
I also need to figure out the cause the CI build failure!
@mbrohl , @ieugen Does it feel like this is going in the right direction?
My motivation for this is to try and make docker images for both developer
testing, demonstrations and something that could potentially be used in
production behind a Traefik reverse-proxy.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
