I have a docker image + docker-compose file which I've been using for a while now. It hosts OFBiz + Postgres and it works great.
It's up to the community to decide if it is interested in moving from the default derby to Postgres and to officially support Docker as the default tool for deploying OFBiz.However, like everything in technology, there is _always_ a tradeoff. So I list my thoughts below in helping you make a choice: Derby pros: - It is simple and familiar to run the default database. Just ./gradlew loadAll and off you go. - Cleaning up is equally simple. ./gradlew cleanAll would wipe out the database - The source code is accessible (not containerized) - The development workflow is known and simple Derby cons: - Users need to get acquainted with how to move to other databases - Most of the testing is done against derby and not the other (more critical) databases like postgres and mysql - Slow (because of the embedded database) - Cannot have multiple connections to the database (I had a few problems in the past because of that) Docker pros: - Very simple to deploy with a single command: docker-compose up -d - Also very simple to cleanup with docker-compose down -v - The environment is consistent regardless of whether this is a developing, staging or production environment - Flexibility in networking and assigning / reassigning ports - Postgres was much faster in data loading. Docker cons: - You need to learn to install docker & docker compose (not too simple) - The development workflow is complex (user access rights on managed vs unmanaged volumes, deployment, integration with gradle). - Need to go through a learning curve for Docker (I would argue that there is a substantial learning curve) - You have locked users to a certain deployment option instead of giving them choice. Docker is not the only solution out there (although it is most common). So there you go, the choice is yours and I hope this comparison might be helpful. On Sat, Dec 16, 2017 at 6:24 PM, Boyden, Timothy <tboy...@electroswitch.com> wrote: > Looks like there is already some working Docker images out on Docker Hub. > None so far suite my current needs (OFBiz with Docker MS SQL 2017 on Linux). > I think I may reach out to opensourceknight and see if he can extend his > image to add the volume /framework/entity/lib/jdbc, so that any JDBC driver, > for any DBMS, can be installed and configured. > > I am currently running trunk from Git locally against a MS SQL 2017 on Linux > Docker image. Works pretty sweet. Now just need OFBiz in a Docker image to > link to the MS SQL instance, and it will be gangbusters. > > -Tim > > -----Original Message----- > From: Paul Mandeltort [mailto:p...@marcospec.com] > Sent: Friday, December 15, 2017 1:37 PM > To: user@ofbiz.apache.org > Subject: RE: Ofbiz to postgresSql connection problem > > Going to second the option of Docker image - I’ve started playing with it but > ran out of time lately. > > A proper docker architecture for ofbiz would be split up as a reference > docker compose file that launches: > - OFbiz Application/Tomcat container > - Database Container - my recommendation is to ditch Derby completely since > deploying postgres as a container is trivial now and the only reason we have > derby (as I understand it) is to simplify initial bring-up of the > application. This can be switched out for a demo-data image that’s already > ready to go or switched to a production image with almost no headaches. > - SOLR container > - Load/Balancer/Http proxy container > > I’ve been toying with this but ran out of time with some other projects on > fire, but want to get back to it as I’m convinced it’ll reduce developer on > boarding effort by an order of magnitude and make it trivial to test and move > deployments between production and development machines. > > —P > > > On Dec 15, 2017, 13:02 -0500, Boyden, Timothy <tboy...@electroswitch.com>, > wrote: >> No problem, hopefully that came across as constructive criticism (as it was >> meant), and not as a rant. >> >> Maybe one possibility is enlisting the help of the jpackage team >> (http://www.jpackage.org/). They have quite the library of Java applications >> that they have repackaged as yum, apt, and rpm installers. >> >> Another possibilty would be reaching out to existing talent in other Apache >> projects, that currently write installers for their projects. >> >> Even nicer would be a Docker image, as that is how most people get up to >> speed on a new application server these days, and would allow a quick path >> to creating a scalable/fault tolerant instance of OFBiz. >> >> Wish I could help out more in this area, but installer package creation is >> not my forte. >> >> Regards, >> >> Tim Boyden >> >> >> -----Original Message----- >> From: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com] >> Sent: Friday, December 15, 2017 11:39 AM >> To: user@ofbiz.apache.org >> Subject: Re: Ofbiz to postgresSql connection problem >> >> Thanks Tim, >> >> Such feedback is valuable for us in order to tune and maintain our >> documentation. >> >> I completely agree, and most of us do, that having a plethoric documentation >> is not a good thing. >> >> I also see that's it's harder to maintain a well structured and up to date >> documentation than to add bricks here and there. >> >> We want to make an effort in this direction in 2018, I hope we will get >> something better. >> >> Help is appreciated, notably about installers, because active committers >> already have a lot to do with the rest. >> >> This said I totally agree and understand your point of view about >> installation. It could be indeed that we are missing attention because we >> neglect this aspect. Actually it's not hard to imagine, just a bit of >> empathy is enough... >> >> Jacques >> >> >> Le 15/12/2017 à 14:22, Boyden, Timothy a écrit : >> > I have to agree, the documentation for setting up OFBiz with an external >> > database is about as clear as mud. For one there are multiple Wiki >> > documents that describe different methods to accomplish the task, rather >> > than one officially accepted method. For example, I tried to follow the >> > Linux (CentOS) version of this Wiki page >> > (https://cwiki.apache.org/confluence/display/OFBIZ/Setup+OFBiz+version+16.11.02+with+PostgreSQL+on+Windows) >> > and the compile command did not properly download and load the driver. >> > However, I had success following the older approach of manually adding the >> > JDBC driver jar file to ${ofbiz install dir}/framework/entity/lib/jdbc as >> > described in this Wiki page ( >> > https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Technical+Production+Setup+Guide#ApacheOFBizTechnicalProductionSetupGuide-DatabaseSetup). >> > Of course, the jar file keeps getting wiped out if you run the cleanAll >> > command. That took a few install attempts to realize, as I fought with DB >> > permission issues. >> > >> > I think more attention in the startup documentation needs to address this >> > issue, rather than a passing comment, that it can (and is even >> > recommended) that the software be setup with an external DBMS. >> > >> > The worst thing you can have, when trying to appeal to ERP solution >> > evaluators, is a software solution that is frustrating to install. A Demo >> > site that doesn't work is the first red flag, but I give that a pass, as >> > we really need to see the software with our own data, in order to fully >> > evaluate it. >> > >> > That is why I am recommending that Yum, Apt, Windows, etc... installers be >> > made available with appropriate install options for clean install and demo >> > install. The software should be installable from software repositories, >> > just like any other modern Linux or Windows application. I have been >> > implementing ERP systems for over 10 years now, and if I didn't like a >> > challenge, would have given up on OFBiz after the first failed install >> > attempt, following the published startup instructions. The last thing an >> > ERP system implementer needs on a go-live weekend, is issues installing >> > the software in the live environment. They already have a huge task ahead >> > of them, getting the business's data loaded in the system. >> > >> > Regards, >> > >> > Tim Boyden >> > >> > >> > >> > -----Original Message----- >> > From: Rishi Solanki [mailto:rishisolan...@gmail.com] >> > Sent: Friday, December 15, 2017 7:05 AM >> > To: ofbizuser <user@ofbiz.apache.org >> > Subject: Re: Ofbiz to postgresSql connection problem >> > >> > Bashir, >> > >> > Are you able to connect postgres version mentioned with specific mentioned >> > driver in pure java class .... please note that here I'm asking to not use >> > OFBiz and connect. >> > If so then we can look into it further. >> > >> > Also please share the OFBiz version and other driver version you are >> > trying with. >> > >> > HTH! >> > >> > >> > Rishi Solanki >> > Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. >> > Direct: +91-9893287847 >> > http://www.hotwaxsystems.com >> > www.hotwax.co >> > >> > On Thu, Dec 14, 2017 at 5:42 AM, bashir.karim...@gmail.com < >> > bashir.karim...@gmail.com> wrote: >> > >> > > Hi Im new to ofbiz and i have some problem in connecting ofbiz to >> > > postgresql version 10, i couldnt find the latest JDBC driver >> > > Version >> > > 42.1.4 in Jcenter, . >> > > i tried other driver from the Jcenter the connection was failed >> > > and couldn't connect to database. >> > > waiting for your help. >> > > >> >>
