Ofbiz 13.04 in Production Build Strategy

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Ofbiz 13.04 in Production Build Strategy

Sakthivel Vellingiri
Hi Ofbiz Users,

- What is the recommended best practice for Ofbiz Production Build
- I have been Playing with Ofbiz for a bit now
     . In my Test/Local environment i build Ofbiz using Ant and start/stop
using shell scripts, from within the project
Reply | Threaded
Open this post in threaded view
|

Re: Ofbiz 13.04 in Production Build Strategy

Sakthivel Vellingiri
Please accept my apologies, mail sent quickly...
    . In essence the entire project including java source
code/configuration is present in the location from which the project is run
    . For Production environment i would like to ONLY include artifacts
that are required for running the project and exclude (Java Source Code etc)
    . How are other Ofbiz users doing Production Build, do we know a list
of artifacts that are required to run the project.
    . Appreciate any pointers or any documentation in this regard,

Regards



On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[hidden email]> wrote:

> Hi Ofbiz Users,
>
> - What is the recommended best practice for Ofbiz Production Build
> - I have been Playing with Ofbiz for a bit now
>      . In my Test/Local environment i build Ofbiz using Ant and start/stop
> using shell scripts, from within the project
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Ofbiz 13.04 in Production Build Strategy

taher
Hi Integrin,

You know I thought about this for a while when deploying to our clients. In
my opinion removing the java source files although easy does not have a lot
of significance because the whole system is open (entities, service
definitions, the controller mappings and so on). Our value proposition is
in delivering requirements rather than in providing propriety solutions.
This only makes a difference if you have a massive java API built on top of
the framework. This of course is my personal opinion.

Taher Alkhateeb
On Oct 17, 2014 5:49 PM, "Integrin" <[hidden email]> wrote:

> Please accept my apologies, mail sent quickly...
>     . In essence the entire project including java source
> code/configuration is present in the location from which the project is run
>     . For Production environment i would like to ONLY include artifacts
> that are required for running the project and exclude (Java Source Code
> etc)
>     . How are other Ofbiz users doing Production Build, do we know a list
> of artifacts that are required to run the project.
>     . Appreciate any pointers or any documentation in this regard,
>
> Regards
>
>
>
> On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[hidden email]>
> wrote:
>
> > Hi Ofbiz Users,
> >
> > - What is the recommended best practice for Ofbiz Production Build
> > - I have been Playing with Ofbiz for a bit now
> >      . In my Test/Local environment i build Ofbiz using Ant and
> start/stop
> > using shell scripts, from within the project
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ofbiz 13.04 in Production Build Strategy

alberto.lobrano
I usually leave the source code on the production server. 

On Fri, Oct 17, 2014 at 5:48 PM, taher [via OFBiz] <[hidden email]> wrote:
Hi Integrin,

You know I thought about this for a while when deploying to our clients. In
my opinion removing the java source files although easy does not have a lot
of significance because the whole system is open (entities, service
definitions, the controller mappings and so on). Our value proposition is
in delivering requirements rather than in providing propriety solutions.
This only makes a difference if you have a massive java API built on top of
the framework. This of course is my personal opinion.

Taher Alkhateeb
On Oct 17, 2014 5:49 PM, "Integrin" <[hidden email]> wrote:

> Please accept my apologies, mail sent quickly...
>     . In essence the entire project including java source
> code/configuration is present in the location from which the project is run
>     . For Production environment i would like to ONLY include artifacts
> that are required for running the project and exclude (Java Source Code
> etc)
>     . How are other Ofbiz users doing Production Build, do we know a list
> of artifacts that are required to run the project.
>     . Appreciate any pointers or any documentation in this regard,
>
> Regards
>
>
>
> On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[hidden email]>
> wrote:
>
> > Hi Ofbiz Users,
> >
> > - What is the recommended best practice for Ofbiz Production Build
> > - I have been Playing with Ofbiz for a bit now
> >      . In my Test/Local environment i build Ofbiz using Ant and
> start/stop
> > using shell scripts, from within the project
> >
> >
>



If you reply to this email, your message will be added to the discussion below:
http://ofbiz.135035.n4.nabble.com/Ofbiz-13-04-in-Production-Build-Strategy-tp4656886p4656898.html
To start a new topic under OFBiz - User, email [hidden email]
To unsubscribe from OFBiz - User, click here.
NAML



--
Alberto Lobrano

Development Manager
Tel: +39 079 998 529
Tel: +39 349 469 4672
Skype: alberto.lobrano

www.integratingweb.com
Reply | Threaded
Open this post in threaded view
|

Re: Ofbiz 13.04 in Production Build Strategy

Sakthivel Vellingiri
In reply to this post by taher
Thanks Taher for sharing your thoughts, I agree with your opinion, while
further evaluating this,
if i were limit the production release artifacts to only Bare Bones
required, seems like Java source code is
the only candidate that is eligible for exclusion, Is this a fair statement?

Regards
Sakthi




On Fri, Oct 17, 2014 at 11:50 AM, Taher Alkhateeb <
[hidden email]> wrote:

> Hi Integrin,
>
> You know I thought about this for a while when deploying to our clients. In
> my opinion removing the java source files although easy does not have a lot
> of significance because the whole system is open (entities, service
> definitions, the controller mappings and so on). Our value proposition is
> in delivering requirements rather than in providing propriety solutions.
> This only makes a difference if you have a massive java API built on top of
> the framework. This of course is my personal opinion.
>
> Taher Alkhateeb
> On Oct 17, 2014 5:49 PM, "Integrin" <[hidden email]> wrote:
>
> > Please accept my apologies, mail sent quickly...
> >     . In essence the entire project including java source
> > code/configuration is present in the location from which the project is
> run
> >     . For Production environment i would like to ONLY include artifacts
> > that are required for running the project and exclude (Java Source Code
> > etc)
> >     . How are other Ofbiz users doing Production Build, do we know a list
> > of artifacts that are required to run the project.
> >     . Appreciate any pointers or any documentation in this regard,
> >
> > Regards
> >
> >
> >
> > On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[hidden email]>
> > wrote:
> >
> > > Hi Ofbiz Users,
> > >
> > > - What is the recommended best practice for Ofbiz Production Build
> > > - I have been Playing with Ofbiz for a bit now
> > >      . In my Test/Local environment i build Ofbiz using Ant and
> > start/stop
> > > using shell scripts, from within the project
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ofbiz 13.04 in Production Build Strategy

taher
Yes close. With a little bit of tweaking i believe you can remove entity
definitions but that is hardly useful. The real value and hard work is in
the user interface, the services (java, groovy, minilang, auto etc...) And
the wiring between them. Most of this stuff is open.
On Oct 17, 2014 7:20 PM, "Integrin" <[hidden email]> wrote:

> Thanks Taher for sharing your thoughts, I agree with your opinion, while
> further evaluating this,
> if i were limit the production release artifacts to only Bare Bones
> required, seems like Java source code is
> the only candidate that is eligible for exclusion, Is this a fair
> statement?
>
> Regards
> Sakthi
>
>
>
>
> On Fri, Oct 17, 2014 at 11:50 AM, Taher Alkhateeb <
> [hidden email]> wrote:
>
> > Hi Integrin,
> >
> > You know I thought about this for a while when deploying to our clients.
> In
> > my opinion removing the java source files although easy does not have a
> lot
> > of significance because the whole system is open (entities, service
> > definitions, the controller mappings and so on). Our value proposition is
> > in delivering requirements rather than in providing propriety solutions.
> > This only makes a difference if you have a massive java API built on top
> of
> > the framework. This of course is my personal opinion.
> >
> > Taher Alkhateeb
> > On Oct 17, 2014 5:49 PM, "Integrin" <[hidden email]> wrote:
> >
> > > Please accept my apologies, mail sent quickly...
> > >     . In essence the entire project including java source
> > > code/configuration is present in the location from which the project is
> > run
> > >     . For Production environment i would like to ONLY include artifacts
> > > that are required for running the project and exclude (Java Source Code
> > > etc)
> > >     . How are other Ofbiz users doing Production Build, do we know a
> list
> > > of artifacts that are required to run the project.
> > >     . Appreciate any pointers or any documentation in this regard,
> > >
> > > Regards
> > >
> > >
> > >
> > > On Fri, Oct 17, 2014 at 10:43 AM, Integrin <[hidden email]>
> > > wrote:
> > >
> > > > Hi Ofbiz Users,
> > > >
> > > > - What is the recommended best practice for Ofbiz Production Build
> > > > - I have been Playing with Ofbiz for a bit now
> > > >      . In my Test/Local environment i build Ofbiz using Ant and
> > > start/stop
> > > > using shell scripts, from within the project
> > > >
> > > >
> > >
> >
>