Hello Eugen, and thanks Pierre for the reminder :) I just wanted to mention there was a previous effort to implement environment variable configuration [1]. This has not yet be pushed into trunk, but is used by our customer projects.
You could check the patch and test if it helps you ease the configuration process. Regards, Gil [1] https://issues.apache.org/jira/browse/OFBIZ-9498 On Thu, Jul 01, 2021 at 10:57:22AM +0200, Pierre Smits wrote: > Hi Ioan, > > My apologies for the late reaction. > > IMO we can forget about the Derby route for this. Derby is not production > grade, and often adopters/implementers already have their preferred RDBMS > for production in play or decided upon. Configuration of such is the > entityengine.xml file, and deployment of such for the various > environments/instances like UAT or PROD can easily managed and deployed via > VCS. > > Best regards, > Pierre Smits > > > On Sun, May 9, 2021 at 9:13 PM Eugen Stan <eugen.s...@netdava.com> wrote: > > > > > > > Hello, > > > > NOTE: I previously sent this email from an un-subscribed email address, > > please ignore that one. > > > > I'm working on a Helm chart for OFBiz > > https://github.com/ieugen/charts/tree/main/ofbiz . > > > > The goal is to have OFBiz running in Kubernetes. > > > > Right now it's a rough start: it starts OFBiz with Derby and that's > > about it. > > > > I'll keep pushing updates as soon as I have them. > > > > I'm interested in your feedback. > > If you plan on testing it and using it let me know. > > I do accept and encourage collaboration. > > > > If this is interesting I might push it upstream but it uses the binary > > build of OFBiz in Docker. > > > > > > I'm using docker images built from trunk on jdk-11. > > There are amd64 and arm64 (Raspberry PI4) images. > > > > Some issues that need solving are the many configuration files that > > OFBiz has. > > > > This details creates a lot of configuration when deploying in Docker / > > Kubernetes as they need to be mounted in a volume with many entries or > > multiple volumes. > > > > There are many potential solutions to this but it boils down to: > > * It would be nice to load max 1-2 or 3 configuration file with multiple > > sections instead of the currently many configs split over the code base. > > * It would be nice to support configuration (overwrite) via ENV vars for > > some things like DB connection. > > > > > > Regards. > > Eugen > >
signature.asc
Description: PGP signature
