discussion:provide official docker image of Apache OFBiz?

[Hans Bakker]

Good morning,

Shouldn't we provide a official docker image in hub.docker.com as most
open source projects do?

This could ease the installation of ofbiz, even with including the
dependencies which is possible with gradle >3.5

To already prepare, I reserved the ofbiz username .

more info at: https://issues.apache.org/jira/browse/OFBIZ-10407

opinions?


--

Regards,

Hans Bakker
CEO, http://antwebsystems.com

[innate Genius]

+1

> On 17-May-2018, at 8:26 AM, Hans Bakker <[hidden email]> wrote:
>
> Good morning,
>
> Shouldn't we provide a official docker image in hub.docker.com as most open source projects do?
>
> This could ease the installation of ofbiz, even with including the dependencies which is possible with gradle >3.5
>
> To already prepare, I reserved the ofbiz username .
>
> more info at: https://issues.apache.org/jira/browse/OFBIZ-10407
>
> opinions?
>
>
> --
>
> Regards,
>
> Hans Bakker
> CEO, http://antwebsystems.com

[deepak nigam-2]

+1.

Please let me know if I can be of any help in this effort.

On Thu, May 17, 2018 at 8:59 AM, innate Genius <[hidden email]>
wrote:

> +1
>
> > On 17-May-2018, at 8:26 AM, Hans Bakker <[hidden email]>
> wrote:
> >
> > Good morning,
> >
> > Shouldn't we provide a official docker image in hub.docker.com as most
> open source projects do?
> >
> > This could ease the installation of ofbiz, even with including the
> dependencies which is possible with gradle >3.5
> >
> > To already prepare, I reserved the ofbiz username .
> >
> > more info at: https://issues.apache.org/jira/browse/OFBIZ-10407
> >
> > opinions?
> >
> >
> > --
> >
> > Regards,
> >
> > Hans Bakker
> > CEO, http://antwebsystems.com
>
>

[Arun Patidar-3]

+1

On Thu, May 17, 2018 at 11:33 AM, deepak nigam <[hidden email]>
wrote:

> +1.
>
> Please let me know if I can be of any help in this effort.
>
> On Thu, May 17, 2018 at 8:59 AM, innate Genius <[hidden email]>
> wrote:
>
> > +1
> >
> > > On 17-May-2018, at 8:26 AM, Hans Bakker <[hidden email]>
> > wrote:
> > >
> > > Good morning,
> > >
> > > Shouldn't we provide a official docker image in hub.docker.com as most
> > open source projects do?
> > >
> > > This could ease the installation of ofbiz, even with including the
> > dependencies which is possible with gradle >3.5
> > >
> > > To already prepare, I reserved the ofbiz username .
> > >
> > > more info at: https://issues.apache.org/jira/browse/OFBIZ-10407
> > >
> > > opinions?
> > >
> > >
> > > --
> > >
> > > Regards,
> > >
> > > Hans Bakker
> > > CEO, http://antwebsystems.com
> >
> >
>

--

Best regards,

Arun Patidar
Director of Information SystemsHotWax Commerce <http://www.hotwax.co/>

[taher]

We need to think and discuss this otherwise I'm not quite sure how much
value people would get from having a docker image. I don't have two docker
files that are identical for the projects we work on because of
customizations and differences.

So to create a docker image you might want to think of some things like:
- what is it used for? Demo purpose? Will it allow loading different data
readers?
- should you allow loading different databases with an accompanying
docker-compose script in the documentation of the image?
- what options / flags should you add to docker image?
- where should we keep the source?
- should we version ofbiz images like is done in some other images?
- how should we structure the volumes for framework and gradle cache?

So I think more details are needed here.

On Thu, May 17, 2018, 9:10 AM Arun Patidar <[hidden email]> wrote:

> +1
>
> On Thu, May 17, 2018 at 11:33 AM, deepak nigam <[hidden email]
> >
> wrote:
>
> > +1.
> >
> > Please let me know if I can be of any help in this effort.
> >
> > On Thu, May 17, 2018 at 8:59 AM, innate Genius <[hidden email]
> >
> > wrote:
> >
> > > +1
> > >
> > > > On 17-May-2018, at 8:26 AM, Hans Bakker <[hidden email]>
> > > wrote:
> > > >
> > > > Good morning,
> > > >
> > > > Shouldn't we provide a official docker image in hub.docker.com as
> most
> > > open source projects do?
> > > >
> > > > This could ease the installation of ofbiz, even with including the
> > > dependencies which is possible with gradle >3.5
> > > >
> > > > To already prepare, I reserved the ofbiz username .
> > > >
> > > > more info at: https://issues.apache.org/jira/browse/OFBIZ-10407
> > > >
> > > > opinions?
> > > >
> > > >
> > > > --
> > > >
> > > > Regards,
> > > >
> > > > Hans Bakker
> > > > CEO, http://antwebsystems.com
> > >
> > >
> >
>
>
>
> --
>
> Best regards,
>
> Arun Patidar
> Director of Information SystemsHotWax Commerce <http://www.hotwax.co/>
>

[marcopaul]

STRONG +1 here as an end user.

Having a solid tested reference implementation would save man years of
time in development, testing, and deployment especially for small
teams that are weak in the devops department.

I started playing with this but it’s a back burner project right now.

A proper set of docker images and a reference docker compose
architecture based around Postgres would be ideal going forward. Then
SOLR could also be managed as a docker image. One of the biggest new
user pain points for ofbiz is figuring out how to switch the database
to a real dbms.  We could then just drop support for derby as the only
reason it’s there is that it supposedly saves time for testing ofbiz.
Docker Postgres solves that problem and is the clear standard for open
source databases now.

Making docker ofbiz the standard starting point also eliminates all
the cross platform java headaches which I see at lest a post or two a
week about.

It would also accelerate adoption, development, and save everyone
money long term as it makes it super easy to fire up and iterate
ofbiz.

—P

> On May 17, 2018, at 1:42 AM, Taher Alkhateeb <[hidden email]> wrote:
>
> We need to think and discuss this otherwise I'm not quite sure how much
> value people would get from having a docker image. I don't have two docker
> files that are identical for the projects we work on because of
> customizations and differences.
>
> So to create a docker image you might want to think of some things like:
> - what is it used for? Demo purpose? Will it allow loading different data
> readers?
> - should you allow loading different databases with an accompanying
> docker-compose script in the documentation of the image?
> - what options / flags should you add to docker image?
> - where should we keep the source?
> - should we version ofbiz images like is done in some other images?
> - how should we structure the volumes for framework and gradle cache?
>
> So I think more details are needed here.
>
>> On Thu, May 17, 2018, 9:10 AM Arun Patidar <[hidden email]> wrote:
>>
>> +1
>>
>> On Thu, May 17, 2018 at 11:33 AM, deepak nigam <[hidden email]
>>>
>> wrote:
>>
>>> +1.
>>>
>>> Please let me know if I can be of any help in this effort.
>>>
>>> On Thu, May 17, 2018 at 8:59 AM, innate Genius <[hidden email]
>>>
>>> wrote:
>>>
>>>> +1
>>>>
>>>>> On 17-May-2018, at 8:26 AM, Hans Bakker <[hidden email]>
>>>> wrote:
>>>>>
>>>>> Good morning,
>>>>>
>>>>> Shouldn't we provide a official docker image in hub.docker.com as
>> most
>>>> open source projects do?
>>>>>
>>>>> This could ease the installation of ofbiz, even with including the
>>>> dependencies which is possible with gradle >3.5
>>>>>
>>>>> To already prepare, I reserved the ofbiz username .
>>>>>
>>>>> more info at: https://issues.apache.org/jira/browse/OFBIZ-10407
>>>>>
>>>>> opinions?
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hans Bakker
>>>>> CEO, http://antwebsystems.com
>>>>
>>>>
>>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> Arun Patidar
>> Director of Information SystemsHotWax Commerce <http://www.hotwax.co/>
>>

[Mathieu Lirzin]

Hello Paul,

Paul Mandeltort <[hidden email]> writes:

> STRONG +1 here as an end user.
>
> Having a solid tested reference implementation would save man years of
> time in development, testing, and deployment especially for small
> teams that are weak in the devops department.
>
> I started playing with this but it’s a back burner project right now.
>
> A proper set of docker images and a reference docker compose
> architecture based around Postgres would be ideal going forward. Then
> SOLR could also be managed as a docker image. One of the biggest new
> user pain points for ofbiz is figuring out how to switch the database
> to a real dbms.  We could then just drop support for derby as the only
> reason it’s there is that it supposedly saves time for testing ofbiz.
> Docker Postgres solves that problem and is the clear standard for open
> source databases now.
>
> Making docker ofbiz the standard starting point also eliminates all
> the cross platform java headaches which I see at lest a post or two a
> week about.
>
> It would also accelerate adoption, development, and save everyone
> money long term as it makes it super easy to fire up and iterate
> ofbiz.

I don't think this kind of incantative tone serves your cause.

Being enthousiastic about a technology is one thing but pretending it
will make everything easy, agile, allow everyone to save money, and
avoid headaches sounds more like bullshit...

IMHO some code, facts, measurements and an enonciation of the necessary
tradeoffs would be more convincing.

--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

[marcopaul]

Probably out of scope for me and the mailing list to sell you on the benefits of containerization, but (in my crappy opinion) there’s a reason that docker is valued at over a billion dollars and all major cloud hosting providers support containers natively now. I think it’s built into some linux distros now.  

I encourage you to try it out and see for yourself:  

1) install docker: https://docs.docker.com/install/ <https://docs.docker.com/install/>
2) docker run -d -p 8080:8080 -p 8443:8443 marcopinball/ofbiz-demo:latest
3) if you want to monitor logs:
        docker ps, find container ID
        docker exec -ti <container id> tail -f /ofbiz/runtime/logs/ofbiz.log
Ta-da, running ofbiz with demo data on https://localhost:8443.

When done just docker rm -f <container id> the container and it’s gone! no cleanup and your system remains unaffected.

This is just OOTB w/ Derby. Want to quickly test ofbiz against a different version of java? Just edit the dockerfile (below) and point it at the java image you want, and run.

This works on Mac, Linux, Windows.

Here’s the docker file and image I slapped together (referenced above) as a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR PRODUCTION READY. Again, I am not an expert here.

It may or may not be best practices but it’s a good starting point for anyone else messing with it:
https://hub.docker.com/r/marcopinball/ofbiz-demo/ <https://hub.docker.com/r/marcopinball/ofbiz-demo/>

—Paul

> On May 17, 2018, at 13:44, Mathieu Lirzin <[hidden email]> wrote:
>
> Hello Paul,
>
> Paul Mandeltort <[hidden email] <mailto:[hidden email]>> writes:
>
>> STRONG +1 here as an end user.
>>
>> Having a solid tested reference implementation would save man years of
>> time in development, testing, and deployment especially for small
>> teams that are weak in the devops department.
>>
>> I started playing with this but it’s a back burner project right now.
>>
>> A proper set of docker images and a reference docker compose
>> architecture based around Postgres would be ideal going forward. Then
>> SOLR could also be managed as a docker image. One of the biggest new
>> user pain points for ofbiz is figuring out how to switch the database
>> to a real dbms.  We could then just drop support for derby as the only
>> reason it’s there is that it supposedly saves time for testing ofbiz.
>> Docker Postgres solves that problem and is the clear standard for open
>> source databases now.
>>
>> Making docker ofbiz the standard starting point also eliminates all
>> the cross platform java headaches which I see at lest a post or two a
>> week about.
>>
>> It would also accelerate adoption, development, and save everyone
>> money long term as it makes it super easy to fire up and iterate
>> ofbiz.
>
> I don't think this kind of incantative tone serves your cause.
>
> Being enthousiastic about a technology is one thing but pretending it
> will make everything easy, agile, allow everyone to save money, and
> avoid headaches sounds more like bullshit...
>
> IMHO some code, facts, measurements and an enonciation of the necessary
> tradeoffs would be more convincing.
>
> --
> Mathieu Lirzin
> GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

[taher]

Hi Paul and everyone:

Two quick notes on your feedback:

1- You can improve your docker file by symlinking the log to stdout, this
way you can view logs with the simple command "docker logs containeridhere"

2- I tried docker as a development platform, and it doesn't really fit that
environment very well. There are too many problems like setting up the IDE,
user permissions, gradle cache issues and so on not to mention that if you
rely on postgres then you must have a docker-compose.yml file. The feedback
loop is also longer and a bit awkward. So perhaps I would not go as far as
saying we should remove derby and only use docker with postgres. For me I
tried that and it wasn't a very smooth experience.

On Fri, May 18, 2018, 3:27 AM Paul Mandeltort <[hidden email]> wrote:

> Probably out of scope for me and the mailing list to sell you on the
> benefits of containerization, but (in my crappy opinion) there’s a reason
> that docker is valued at over a billion dollars and all major cloud hosting
> providers support containers natively now. I think it’s built into some
> linux distros now.
>
> I encourage you to try it out and see for yourself:
>
> 1) install docker: https://docs.docker.com/install/ <
> https://docs.docker.com/install/>
> 2) docker run -d -p 8080:8080 -p 8443:8443 marcopinball/ofbiz-demo:latest
> 3) if you want to monitor logs:
>         docker ps, find container ID
>           docker exec -ti <container id> tail -f
> /ofbiz/runtime/logs/ofbiz.log
> Ta-da, running ofbiz with demo data on https://localhost:8443.
>
> When done just docker rm -f <container id> the container and it’s gone! no
> cleanup and your system remains unaffected.
>
> This is just OOTB w/ Derby. Want to quickly test ofbiz against a different
> version of java? Just edit the dockerfile (below) and point it at the java
> image you want, and run.
>
> This works on Mac, Linux, Windows.
>
> Here’s the docker file and image I slapped together (referenced above) as
> a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR
> PRODUCTION READY. Again, I am not an expert here.
>
> It may or may not be best practices but it’s a good starting point for
> anyone else messing with it:
> https://hub.docker.com/r/marcopinball/ofbiz-demo/ <
> https://hub.docker.com/r/marcopinball/ofbiz-demo/>
>
> —Paul
>
> > On May 17, 2018, at 13:44, Mathieu Lirzin <[hidden email]>
> wrote:
> >
> > Hello Paul,
> >
> > Paul Mandeltort <[hidden email] <mailto:[hidden email]>> writes:
> >
> >> STRONG +1 here as an end user.
> >>
> >> Having a solid tested reference implementation would save man years of
> >> time in development, testing, and deployment especially for small
> >> teams that are weak in the devops department.
> >>
> >> I started playing with this but it’s a back burner project right now.
> >>
> >> A proper set of docker images and a reference docker compose
> >> architecture based around Postgres would be ideal going forward. Then
> >> SOLR could also be managed as a docker image. One of the biggest new
> >> user pain points for ofbiz is figuring out how to switch the database
> >> to a real dbms.  We could then just drop support for derby as the only
> >> reason it’s there is that it supposedly saves time for testing ofbiz.
> >> Docker Postgres solves that problem and is the clear standard for open
> >> source databases now.
> >>
> >> Making docker ofbiz the standard starting point also eliminates all
> >> the cross platform java headaches which I see at lest a post or two a
> >> week about.
> >>
> >> It would also accelerate adoption, development, and save everyone
> >> money long term as it makes it super easy to fire up and iterate
> >> ofbiz.
> >
> > I don't think this kind of incantative tone serves your cause.
> >
> > Being enthousiastic about a technology is one thing but pretending it
> > will make everything easy, agile, allow everyone to save money, and
> > avoid headaches sounds more like bullshit...
> >
> > IMHO some code, facts, measurements and an enonciation of the necessary
> > tradeoffs would be more convincing.
> >
> > --
> > Mathieu Lirzin
> > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
>
>

[deepak nigam-2]

Hi All,

I also tried docker as a development platform by bind-mounting my custom
plugins folder with docker container's plugins folder. It was a good
experience for me, however, I did it just for a PoC. Here is the same
command I used for mounting:

docker run -it --name=docker-ofbiz -d -v  ~/plugins/:/ofbiz-17.12/plugins
-p 8080:8080 -p 8443:8443 ofbiz/full-trunk



On Fri, May 18, 2018 at 12:55 PM Taher Alkhateeb <[hidden email]>
wrote:

> Hi Paul and everyone:
>
> Two quick notes on your feedback:
>
> 1- You can improve your docker file by symlinking the log to stdout, this
> way you can view logs with the simple command "docker logs containeridhere"
>
> 2- I tried docker as a development platform, and it doesn't really fit that
> environment very well. There are too many problems like setting up the IDE,
> user permissions, gradle cache issues and so on not to mention that if you
> rely on postgres then you must have a docker-compose.yml file. The feedback
> loop is also longer and a bit awkward. So perhaps I would not go as far as
> saying we should remove derby and only use docker with postgres. For me I
> tried that and it wasn't a very smooth experience.
>
> On Fri, May 18, 2018, 3:27 AM Paul Mandeltort <[hidden email]> wrote:
>
> > Probably out of scope for me and the mailing list to sell you on the
> > benefits of containerization, but (in my crappy opinion) there’s a reason
> > that docker is valued at over a billion dollars and all major cloud
> hosting
> > providers support containers natively now. I think it’s built into some
> > linux distros now.
> >
> > I encourage you to try it out and see for yourself:
> >
> > 1) install docker: https://docs.docker.com/install/ <
> > https://docs.docker.com/install/>
> > 2) docker run -d -p 8080:8080 -p 8443:8443 marcopinball/ofbiz-demo:latest
> > 3) if you want to monitor logs:
> >         docker ps, find container ID
> >           docker exec -ti <container id> tail -f
> > /ofbiz/runtime/logs/ofbiz.log
> > Ta-da, running ofbiz with demo data on https://localhost:8443.
> >
> > When done just docker rm -f <container id> the container and it’s gone!
> no
> > cleanup and your system remains unaffected.
> >
> > This is just OOTB w/ Derby. Want to quickly test ofbiz against a
> different
> > version of java? Just edit the dockerfile (below) and point it at the
> java
> > image you want, and run.
> >
> > This works on Mac, Linux, Windows.
> >
> > Here’s the docker file and image I slapped together (referenced above) as
> > a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR
> > PRODUCTION READY. Again, I am not an expert here.
> >
> > It may or may not be best practices but it’s a good starting point for
> > anyone else messing with it:
> > https://hub.docker.com/r/marcopinball/ofbiz-demo/ <
> > https://hub.docker.com/r/marcopinball/ofbiz-demo/>
> >
> > —Paul
> >
> > > On May 17, 2018, at 13:44, Mathieu Lirzin <[hidden email]>
> > wrote:
> > >
> > > Hello Paul,
> > >
> > > Paul Mandeltort <[hidden email] <mailto:[hidden email]>>
> writes:
> > >
> > >> STRONG +1 here as an end user.
> > >>
> > >> Having a solid tested reference implementation would save man years of
> > >> time in development, testing, and deployment especially for small
> > >> teams that are weak in the devops department.
> > >>
> > >> I started playing with this but it’s a back burner project right now.
> > >>
> > >> A proper set of docker images and a reference docker compose
> > >> architecture based around Postgres would be ideal going forward. Then
> > >> SOLR could also be managed as a docker image. One of the biggest new
> > >> user pain points for ofbiz is figuring out how to switch the database
> > >> to a real dbms.  We could then just drop support for derby as the only
> > >> reason it’s there is that it supposedly saves time for testing ofbiz.
> > >> Docker Postgres solves that problem and is the clear standard for open
> > >> source databases now.
> > >>
> > >> Making docker ofbiz the standard starting point also eliminates all
> > >> the cross platform java headaches which I see at lest a post or two a
> > >> week about.
> > >>
> > >> It would also accelerate adoption, development, and save everyone
> > >> money long term as it makes it super easy to fire up and iterate
> > >> ofbiz.
> > >
> > > I don't think this kind of incantative tone serves your cause.
> > >
> > > Being enthousiastic about a technology is one thing but pretending it
> > > will make everything easy, agile, allow everyone to save money, and
> > > avoid headaches sounds more like bullshit...
> > >
> > > IMHO some code, facts, measurements and an enonciation of the necessary
> > > tradeoffs would be more convincing.
> > >
> > > --
> > > Mathieu Lirzin
> > > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
> >
> >
>

Hello and thank you. I recently downloaded the image, ofbiz/fulltrunk, to see if ofbiz would meet my needs and it appears that it will far exceed them! Is there a way to run a docker without the sample data? I fully believe the stock db will be plenty for my needs especially if I can start with an empty version or scrub the current data.

I want to run ofbiz in a docker container rather than a standalone.

On 2018/06/23 05:17:41, deepak nigam <[hidden email]> wrote:

> Hi All,
>
> I also tried docker as a development platform by bind-mounting my custom
> plugins folder with docker container's plugins folder. It was a good
> experience for me, however, I did it just for a PoC. Here is the same
> command I used for mounting:
>
> docker run -it --name=docker-ofbiz -d -v  ~/plugins/:/ofbiz-17.12/plugins
> -p 8080:8080 -p 8443:8443 ofbiz/full-trunk
>
>
>
> On Fri, May 18, 2018 at 12:55 PM Taher Alkhateeb <[hidden email]>
> wrote:
>
> > Hi Paul and everyone:
> >
> > Two quick notes on your feedback:
> >
> > 1- You can improve your docker file by symlinking the log to stdout, this
> > way you can view logs with the simple command "docker logs containeridhere"
> >
> > 2- I tried docker as a development platform, and it doesn't really fit that
> > environment very well. There are too many problems like setting up the IDE,
> > user permissions, gradle cache issues and so on not to mention that if you
> > rely on postgres then you must have a docker-compose.yml file. The feedback
> > loop is also longer and a bit awkward. So perhaps I would not go as far as
> > saying we should remove derby and only use docker with postgres. For me I
> > tried that and it wasn't a very smooth experience.
> >
> > On Fri, May 18, 2018, 3:27 AM Paul Mandeltort <[hidden email]> wrote:
> >
> > > Probably out of scope for me and the mailing list to sell you on the
> > > benefits of containerization, but (in my crappy opinion) there’s a reason
> > > that docker is valued at over a billion dollars and all major cloud
> > hosting
> > > providers support containers natively now. I think it’s built into some
> > > linux distros now.
> > >
> > > I encourage you to try it out and see for yourself:
> > >
> > > 1) install docker: https://docs.docker.com/install/ <
> > > https://docs.docker.com/install/>
> > > 2) docker run -d -p 8080:8080 -p 8443:8443 marcopinball/ofbiz-demo:latest
> > > 3) if you want to monitor logs:
> > >         docker ps, find container ID
> > >           docker exec -ti <container id> tail -f
> > > /ofbiz/runtime/logs/ofbiz.log
> > > Ta-da, running ofbiz with demo data on https://localhost:8443.
> > >
> > > When done just docker rm -f <container id> the container and it’s gone!
> > no
> > > cleanup and your system remains unaffected.
> > >
> > > This is just OOTB w/ Derby. Want to quickly test ofbiz against a
> > different
> > > version of java? Just edit the dockerfile (below) and point it at the
> > java
> > > image you want, and run.
> > >
> > > This works on Mac, Linux, Windows.
> > >
> > > Here’s the docker file and image I slapped together (referenced above) as
> > > a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR
> > > PRODUCTION READY. Again, I am not an expert here.
> > >
> > > It may or may not be best practices but it’s a good starting point for
> > > anyone else messing with it:
> > > https://hub.docker.com/r/marcopinball/ofbiz-demo/ <
> > > https://hub.docker.com/r/marcopinball/ofbiz-demo/>
> > >
> > > —Paul
> > >
> > > > On May 17, 2018, at 13:44, Mathieu Lirzin <[hidden email]>
> > > wrote:
> > > >
> > > > Hello Paul,
> > > >
> > > > Paul Mandeltort <[hidden email] <mailto:[hidden email]>>
> > writes:
> > > >
> > > >> STRONG +1 here as an end user.
> > > >>
> > > >> Having a solid tested reference implementation would save man years of
> > > >> time in development, testing, and deployment especially for small
> > > >> teams that are weak in the devops department.
> > > >>
> > > >> I started playing with this but it’s a back burner project right now.
> > > >>
> > > >> A proper set of docker images and a reference docker compose
> > > >> architecture based around Postgres would be ideal going forward. Then
> > > >> SOLR could also be managed as a docker image. One of the biggest new
> > > >> user pain points for ofbiz is figuring out how to switch the database
> > > >> to a real dbms.  We could then just drop support for derby as the only
> > > >> reason it’s there is that it supposedly saves time for testing ofbiz.
> > > >> Docker Postgres solves that problem and is the clear standard for open
> > > >> source databases now.
> > > >>
> > > >> Making docker ofbiz the standard starting point also eliminates all
> > > >> the cross platform java headaches which I see at lest a post or two a
> > > >> week about.
> > > >>
> > > >> It would also accelerate adoption, development, and save everyone
> > > >> money long term as it makes it super easy to fire up and iterate
> > > >> ofbiz.
> > > >
> > > > I don't think this kind of incantative tone serves your cause.
> > > >
> > > > Being enthousiastic about a technology is one thing but pretending it
> > > > will make everything easy, agile, allow everyone to save money, and
> > > > avoid headaches sounds more like bullshit...
> > > >
> > > > IMHO some code, facts, measurements and an enonciation of the necessary
> > > > tradeoffs would be more convincing.
> > > >
> > > > --
> > > > Mathieu Lirzin
> > > > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
> > >
> > >
> >

[Deepak Dixit-4]

Hi User,

Your email has been moderated, Please subscribe to the mailing list
http://ofbiz.apache.org/mailing-lists.html

Thanks & Regards
--
Deepak Dixit


On Sun, Nov 4, 2018 at 6:34 AM, [hidden email] <
[hidden email]> wrote:

> Hello and thank you. I recently downloaded the image, ofbiz/fulltrunk, to
> see if ofbiz would meet my needs and it appears that it will far exceed
> them! Is there a way to run a docker without the sample data? I fully
> believe the stock db will be plenty for my needs especially if I can start
> with an empty version or scrub the current data.
>
> I want to run ofbiz in a docker container rather than a standalone.
>
> On 2018/06/23 05:17:41, deepak nigam <[hidden email]> wrote:
> > Hi All,
> >
> > I also tried docker as a development platform by bind-mounting my custom
> > plugins folder with docker container's plugins folder. It was a good
> > experience for me, however, I did it just for a PoC. Here is the same
> > command I used for mounting:
> >
> > docker run -it --name=docker-ofbiz -d -v  ~/plugins/:/ofbiz-17.12/
> plugins
> > -p 8080:8080 -p 8443:8443 ofbiz/full-trunk
> >
> >
> >
> > On Fri, May 18, 2018 at 12:55 PM Taher Alkhateeb <
> [hidden email]>
> > wrote:
> >
> > > Hi Paul and everyone:
> > >
> > > Two quick notes on your feedback:
> > >
> > > 1- You can improve your docker file by symlinking the log to stdout,
> this
> > > way you can view logs with the simple command "docker logs
> containeridhere"
> > >
> > > 2- I tried docker as a development platform, and it doesn't really fit
> that
> > > environment very well. There are too many problems like setting up the
> IDE,
> > > user permissions, gradle cache issues and so on not to mention that if
> you
> > > rely on postgres then you must have a docker-compose.yml file. The
> feedback
> > > loop is also longer and a bit awkward. So perhaps I would not go as
> far as
> > > saying we should remove derby and only use docker with postgres. For
> me I
> > > tried that and it wasn't a very smooth experience.
> > >
> > > On Fri, May 18, 2018, 3:27 AM Paul Mandeltort <[hidden email]>
> wrote:
> > >
> > > > Probably out of scope for me and the mailing list to sell you on the
> > > > benefits of containerization, but (in my crappy opinion) there’s a
> reason
> > > > that docker is valued at over a billion dollars and all major cloud
> > > hosting
> > > > providers support containers natively now. I think it’s built into
> some
> > > > linux distros now.
> > > >
> > > > I encourage you to try it out and see for yourself:
> > > >
> > > > 1) install docker: https://docs.docker.com/install/ <
> > > > https://docs.docker.com/install/>
> > > > 2) docker run -d -p 8080:8080 -p 8443:8443
> marcopinball/ofbiz-demo:latest
> > > > 3) if you want to monitor logs:
> > > >         docker ps, find container ID
> > > >           docker exec -ti <container id> tail -f
> > > > /ofbiz/runtime/logs/ofbiz.log
> > > > Ta-da, running ofbiz with demo data on https://localhost:8443.
> > > >
> > > > When done just docker rm -f <container id> the container and it’s
> gone!
> > > no
> > > > cleanup and your system remains unaffected.
> > > >
> > > > This is just OOTB w/ Derby. Want to quickly test ofbiz against a
> > > different
> > > > version of java? Just edit the dockerfile (below) and point it at the
> > > java
> > > > image you want, and run.
> > > >
> > > > This works on Mac, Linux, Windows.
> > > >
> > > > Here’s the docker file and image I slapped together (referenced
> above) as
> > > > a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR
> > > > PRODUCTION READY. Again, I am not an expert here.
> > > >
> > > > It may or may not be best practices but it’s a good starting point
> for
> > > > anyone else messing with it:
> > > > https://hub.docker.com/r/marcopinball/ofbiz-demo/ <
> > > > https://hub.docker.com/r/marcopinball/ofbiz-demo/>
> > > >
> > > > —Paul
> > > >
> > > > > On May 17, 2018, at 13:44, Mathieu Lirzin <
> [hidden email]>
> > > > wrote:
> > > > >
> > > > > Hello Paul,
> > > > >
> > > > > Paul Mandeltort <[hidden email] <mailto:[hidden email]>>
> > > writes:
> > > > >
> > > > >> STRONG +1 here as an end user.
> > > > >>
> > > > >> Having a solid tested reference implementation would save man
> years of
> > > > >> time in development, testing, and deployment especially for small
> > > > >> teams that are weak in the devops department.
> > > > >>
> > > > >> I started playing with this but it’s a back burner project right
> now.
> > > > >>
> > > > >> A proper set of docker images and a reference docker compose
> > > > >> architecture based around Postgres would be ideal going forward.
> Then
> > > > >> SOLR could also be managed as a docker image. One of the biggest
> new
> > > > >> user pain points for ofbiz is figuring out how to switch the
> database
> > > > >> to a real dbms.  We could then just drop support for derby as the
> only
> > > > >> reason it’s there is that it supposedly saves time for testing
> ofbiz.
> > > > >> Docker Postgres solves that problem and is the clear standard for
> open
> > > > >> source databases now.
> > > > >>
> > > > >> Making docker ofbiz the standard starting point also eliminates
> all
> > > > >> the cross platform java headaches which I see at lest a post or
> two a
> > > > >> week about.
> > > > >>
> > > > >> It would also accelerate adoption, development, and save everyone
> > > > >> money long term as it makes it super easy to fire up and iterate
> > > > >> ofbiz.
> > > > >
> > > > > I don't think this kind of incantative tone serves your cause.
> > > > >
> > > > > Being enthousiastic about a technology is one thing but pretending
> it
> > > > > will make everything easy, agile, allow everyone to save money, and
> > > > > avoid headaches sounds more like bullshit...
> > > > >
> > > > > IMHO some code, facts, measurements and an enonciation of the
> necessary
> > > > > tradeoffs would be more convincing.
> > > > >
> > > > > --
> > > > > Mathieu Lirzin
> > > > > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
> > > >
> > > >
> > >
>

[deepak nigam-2]

Hi Jonhson,

For this, you can apply a hook into a running Docker container using the
command "docker exec -it <container> bash". Basically, you need to
configure your EntityEngine.xml file for using the stock DB. For more
information on how to configure EntityEngine.xml, please visit here
<https://cwiki.apache.org/confluence/display/OFBIZ/Entity+Engine+Configuration+Guide>
.

As for as the sample data is concerned, you can exclude the demo data
reader from the gradle target used to load data. (i.e. don't use ./gradlew
loadAll, use specific one ./gradlew "ofbiz --load-data
readers=seed,seed-initial,ext-seed,ext"). You need to run this command from
the root of your project in the container.


HTH!

Thanks & Regards
Deepak Nigam
HotWax Systems Pvt. Ltd.




On Mon, Nov 5, 2018 at 10:17 AM [hidden email] <
[hidden email]> wrote:

> Hello and thank you. I recently downloaded the image, ofbiz/fulltrunk, to
> see if ofbiz would meet my needs and it appears that it will far exceed
> them! Is there a way to run a docker without the sample data? I fully
> believe the stock db will be plenty for my needs especially if I can start
> with an empty version or scrub the current data.
>
> I want to run ofbiz in a docker container rather than a standalone.
>
> On 2018/06/23 05:17:41, deepak nigam <[hidden email]> wrote:
> > Hi All,
> >
> > I also tried docker as a development platform by bind-mounting my custom
> > plugins folder with docker container's plugins folder. It was a good
> > experience for me, however, I did it just for a PoC. Here is the same
> > command I used for mounting:
> >
> > docker run -it --name=docker-ofbiz -d -v  ~/plugins/:/ofbiz-17.12/plugins
> > -p 8080:8080 -p 8443:8443 ofbiz/full-trunk
> >
> >
> >
> > On Fri, May 18, 2018 at 12:55 PM Taher Alkhateeb <
> [hidden email]>
> > wrote:
> >
> > > Hi Paul and everyone:
> > >
> > > Two quick notes on your feedback:
> > >
> > > 1- You can improve your docker file by symlinking the log to stdout,
> this
> > > way you can view logs with the simple command "docker logs
> containeridhere"
> > >
> > > 2- I tried docker as a development platform, and it doesn't really fit
> that
> > > environment very well. There are too many problems like setting up the
> IDE,
> > > user permissions, gradle cache issues and so on not to mention that if
> you
> > > rely on postgres then you must have a docker-compose.yml file. The
> feedback
> > > loop is also longer and a bit awkward. So perhaps I would not go as
> far as
> > > saying we should remove derby and only use docker with postgres. For
> me I
> > > tried that and it wasn't a very smooth experience.
> > >
> > > On Fri, May 18, 2018, 3:27 AM Paul Mandeltort <[hidden email]>
> wrote:
> > >
> > > > Probably out of scope for me and the mailing list to sell you on the
> > > > benefits of containerization, but (in my crappy opinion) there’s a
> reason
> > > > that docker is valued at over a billion dollars and all major cloud
> > > hosting
> > > > providers support containers natively now. I think it’s built into
> some
> > > > linux distros now.
> > > >
> > > > I encourage you to try it out and see for yourself:
> > > >
> > > > 1) install docker: https://docs.docker.com/install/ <
> > > > https://docs.docker.com/install/>
> > > > 2) docker run -d -p 8080:8080 -p 8443:8443
> marcopinball/ofbiz-demo:latest
> > > > 3) if you want to monitor logs:
> > > >         docker ps, find container ID
> > > >           docker exec -ti <container id> tail -f
> > > > /ofbiz/runtime/logs/ofbiz.log
> > > > Ta-da, running ofbiz with demo data on https://localhost:8443.
> > > >
> > > > When done just docker rm -f <container id> the container and it’s
> gone!
> > > no
> > > > cleanup and your system remains unaffected.
> > > >
> > > > This is just OOTB w/ Derby. Want to quickly test ofbiz against a
> > > different
> > > > version of java? Just edit the dockerfile (below) and point it at the
> > > java
> > > > image you want, and run.
> > > >
> > > > This works on Mac, Linux, Windows.
> > > >
> > > > Here’s the docker file and image I slapped together (referenced
> above) as
> > > > a proof of concept. IT SHOULD NOT BE CONSIDERED BEST PRACTICES OR
> > > > PRODUCTION READY. Again, I am not an expert here.
> > > >
> > > > It may or may not be best practices but it’s a good starting point
> for
> > > > anyone else messing with it:
> > > > https://hub.docker.com/r/marcopinball/ofbiz-demo/ <
> > > > https://hub.docker.com/r/marcopinball/ofbiz-demo/>
> > > >
> > > > —Paul
> > > >
> > > > > On May 17, 2018, at 13:44, Mathieu Lirzin <
> [hidden email]>
> > > > wrote:
> > > > >
> > > > > Hello Paul,
> > > > >
> > > > > Paul Mandeltort <[hidden email] <mailto:[hidden email]>>
> > > writes:
> > > > >
> > > > >> STRONG +1 here as an end user.
> > > > >>
> > > > >> Having a solid tested reference implementation would save man
> years of
> > > > >> time in development, testing, and deployment especially for small
> > > > >> teams that are weak in the devops department.
> > > > >>
> > > > >> I started playing with this but it’s a back burner project right
> now.
> > > > >>
> > > > >> A proper set of docker images and a reference docker compose
> > > > >> architecture based around Postgres would be ideal going forward.
> Then
> > > > >> SOLR could also be managed as a docker image. One of the biggest
> new
> > > > >> user pain points for ofbiz is figuring out how to switch the
> database
> > > > >> to a real dbms.  We could then just drop support for derby as the
> only
> > > > >> reason it’s there is that it supposedly saves time for testing
> ofbiz.
> > > > >> Docker Postgres solves that problem and is the clear standard for
> open
> > > > >> source databases now.
> > > > >>
> > > > >> Making docker ofbiz the standard starting point also eliminates
> all
> > > > >> the cross platform java headaches which I see at lest a post or
> two a
> > > > >> week about.
> > > > >>
> > > > >> It would also accelerate adoption, development, and save everyone
> > > > >> money long term as it makes it super easy to fire up and iterate
> > > > >> ofbiz.
> > > > >
> > > > > I don't think this kind of incantative tone serves your cause.
> > > > >
> > > > > Being enthousiastic about a technology is one thing but pretending
> it
> > > > > will make everything easy, agile, allow everyone to save money, and
> > > > > avoid headaches sounds more like bullshit...
> > > > >
> > > > > IMHO some code, facts, measurements and an enonciation of the
> necessary
> > > > > tradeoffs would be more convincing.
> > > > >
> > > > > --
> > > > > Mathieu Lirzin
> > > > > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
> > > >
> > > >
> > >
>