These days we are mostly working in Kubernetes. Docker only takes you part
way to the horizontal scalability promised land.

On Tue, Dec 1, 2020 at 12:27 PM Eugen Stan <eugen.s...@netdava.com> wrote:

> Hi,
>
> There has been some discussion regarding Docker and OFBiz, however no
> consensus yet.
> I'm starting this thread after discussions on Slack with Jacques Le
> Roux, Daniel Watford and Michael Brohl.
>
> The the aim to establish some goals / objectives regarding Docker and
> OFBiz.
>
> Please add your feedback, comments and suggestions.
>
> Prior work regarding this is found
>
> https://issues.apache.org/jira/browse/OFBIZ-10407
>
> https://lists.apache.org/thread.html/r40fd679818a37e113b469add51755b1097a2b02d3961e71a2cfe928d%40%3Cdev.ofbiz.apache.org%3E
>
> and in the links stemming from the links above.
>
> ----
>
> == How can we integrate Docker in OFBiz ?
>
> Docker can be used in two distinct ways:
>
> a. Use Docker as a way to build OFBiz components - this will make builds
> more portable - as long as people have Docker (or containerd or podman)
> installed locally, they will be able to build OFBiz "for sure" (tm).
>
> This aims to solve the issue of people not having  the proper JDK and
> required tools installed (gradle, git ?! etc).
>
> b. Use Docker to deploy OFBiz for production purposes (and demos)
> IMO this means building a slim Docker image with only JRE and OFBiz + a
> custom selection of plugins. IMO this is best achieved with pre-built,
> published binaries for ofbiz.
>
> c. Use Docker to develop / debug OFBiz
> I'm not sure if this is really a thing since IMO falls into b).
>
>
> Using docker multi stage image builds is something that could help.
>
> The goals are sometimes at odds with one another in the sense that doing
> something to fix a goal will hinder the other.
>
> Do you see other use-cases for Docker and OFBiz?
>
>
> == My personal take
>
> Personally I would like to focus on b). I did not have good experience
> with building sources with Docker - I could not get used to the workflow.
>
> Also when I deploy to production, I don't really care how it's built as
> long as I have the binary and I can run just that.
>
> So we might end up with two or more Dockerfiles, each focusing on
> specific objectives.
>
>
>
> Regards,
> --
> Eugen Stan
> +40720 898 747 / netdava.com
>


-- 
Ean Schuessler, Brainfood Co-Founder
e...@brainfood.com
214-720-0700

Reply via email to