Debian Package Of OFBiz

[Justin Dagostino]

Hi,

I'm exploring some production deployment options that don't involve
installing SVN, Ant, etc. on the production servers.  Aside from TAR'ing up
the entire project, copying it over, and un-packaging, etc., perhaps
creating an installable OS package is a more elegant solution.

I came across the "debian" folder in OFBiz.  First, is this meant to
provide the building blocks for creating an OFBiz Debian package?  If not,
can anyone provide some insight in accomplishing such a task?

Any help would be greatly appreciated.  Thank you.


Justin

[Jacques Le Roux]

It was a WIP by Adam Heath but was discontinued recently
https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic#OFBizAttic-Debian

Jacques

Justin Dagostino wrote:

> Hi,
>
> I'm exploring some production deployment options that don't involve
> installing SVN, Ant, etc. on the production servers.  Aside from TAR'ing up
> the entire project, copying it over, and un-packaging, etc., perhaps
> creating an installable OS package is a more elegant solution.
>
> I came across the "debian" folder in OFBiz.  First, is this meant to
> provide the building blocks for creating an OFBiz Debian package?  If not,
> can anyone provide some insight in accomplishing such a task?
>
> Any help would be greatly appreciated.  Thank you.
>
>
> Justin

[Justin Dagostino]

Bummer.

What is the preferred approach to deploying OFBiz?   Is it tar/zip the
entire OFBiz folder structure, copy, and extract??


On Tue, Oct 22, 2013 at 4:42 PM, Jacques Le Roux <
[hidden email]> wrote:

> It was a WIP by Adam Heath but was discontinued recently
>
> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic#OFBizAttic-Debian
>
> Jacques
>
> Justin Dagostino wrote:
> > Hi,
> >
> > I'm exploring some production deployment options that don't involve
> > installing SVN, Ant, etc. on the production servers.  Aside from TAR'ing
> up
> > the entire project, copying it over, and un-packaging, etc., perhaps
> > creating an installable OS package is a more elegant solution.
> >
> > I came across the "debian" folder in OFBiz.  First, is this meant to
> > provide the building blocks for creating an OFBiz Debian package?  If
> not,
> > can anyone provide some insight in accomplishing such a task?
> >
> > Any help would be greatly appreciated.  Thank you.
> >
> >
> > Justin
>

[Jacques Le Roux]

Personally I prefer to begin with a svn checkout either from the trunk or a branch. So you can stay updated.
Then later when creating your own repo you can cut this link or use svn external (sensitive). Of course using a release branch is safer.
Note that this stratey is easier for me, because I can directly commit in the OFBiz repo, YMMV.

There are other strategies https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branch that you may adapt to your needs

You might also not bother, extract from a package and forget it...

Jacques

Justin Dagostino wrote:

> Bummer.
>
> What is the preferred approach to deploying OFBiz?   Is it tar/zip the
> entire OFBiz folder structure, copy, and extract??
>
>
> On Tue, Oct 22, 2013 at 4:42 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> It was a WIP by Adam Heath but was discontinued recently
>>
>> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic#OFBizAttic-Debian
>>
>> Jacques
>>
>> Justin Dagostino wrote:
>>> Hi,
>>>
>>> I'm exploring some production deployment options that don't involve
>>> installing SVN, Ant, etc. on the production servers.  Aside from TAR'ing up
>>> the entire project, copying it over, and un-packaging, etc., perhaps
>>> creating an installable OS package is a more elegant solution.
>>>
>>> I came across the "debian" folder in OFBiz.  First, is this meant to
>>> provide the building blocks for creating an OFBiz Debian package?  If not,
>>> can anyone provide some insight in accomplishing such a task?
>>>
>>> Any help would be greatly appreciated.  Thank you.
>>>
>>>
>>> Justin

[Justin Dagostino]

Thanks again for the reply and the link.   One thing that is not 100% clear
is whether or not people are actually checking out from SVN (from whatever
branch) directly on production (and possibly running Ant tasks there as
well).  I'd really like to avoid that.

If that's not what you are suggesting, do you recommend using the
vendor/branch strategy on a development server and then promoting it to the
other various environments, including production, by archive/pack, copy to
the target environment(s), and unpacking on the target?


J

[Adrian Crum-3]

If you don't want to use SVN or Ant on your production server, then you
have no choice - you must build it somewhere else and then copy it to
the production server.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 10/23/2013 2:04 PM, Justin Dagostino wrote:

> Thanks again for the reply and the link.   One thing that is not 100% clear
> is whether or not people are actually checking out from SVN (from whatever
> branch) directly on production (and possibly running Ant tasks there as
> well).  I'd really like to avoid that.
>
> If that's not what you are suggesting, do you recommend using the
> vendor/branch strategy on a development server and then promoting it to the
> other various environments, including production, by archive/pack, copy to
> the target environment(s), and unpacking on the target?
>
>
> J
>
>

[Justin Dagostino]

Thanks.   Just confirming my assumptions.  I liked the Debian package
management possibility, but it's been retired (and maybe should be removed
from the framework).


On Wed, Oct 23, 2013 at 5:11 PM, Adrian Crum <
[hidden email]> wrote:

> If you don't want to use SVN or Ant on your production server, then you
> have no choice - you must build it somewhere else and then copy it to the
> production server.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
>
> On 10/23/2013 2:04 PM, Justin Dagostino wrote:
>
>> Thanks again for the reply and the link.   One thing that is not 100%
>> clear
>> is whether or not people are actually checking out from SVN (from whatever
>> branch) directly on production (and possibly running Ant tasks there as
>> well).  I'd really like to avoid that.
>>
>> If that's not what you are suggesting, do you recommend using the
>> vendor/branch strategy on a development server and then promoting it to
>> the
>> other various environments, including production, by archive/pack, copy to
>> the target environment(s), and unpacking on the target?
>>
>>
>> J
>>
>>
>>

[Adrian Crum-3]

These questions are a subset of questions that can be answered with a
comprehensive SDLC process document. If you don't have one already, I
recommend that you create one.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 10/23/2013 2:16 PM, Justin Dagostino wrote:

> Thanks.   Just confirming my assumptions.  I liked the Debian package
> management possibility, but it's been retired (and maybe should be removed
> from the framework).
>
>
> On Wed, Oct 23, 2013 at 5:11 PM, Adrian Crum <
> [hidden email]> wrote:
>
>> If you don't want to use SVN or Ant on your production server, then you
>> have no choice - you must build it somewhere else and then copy it to the
>> production server.
>>
>> Adrian Crum
>> Sandglass Software
>> www.sandglass-software.com
>>
>>
>> On 10/23/2013 2:04 PM, Justin Dagostino wrote:
>>
>>> Thanks again for the reply and the link.   One thing that is not 100%
>>> clear
>>> is whether or not people are actually checking out from SVN (from whatever
>>> branch) directly on production (and possibly running Ant tasks there as
>>> well).  I'd really like to avoid that.
>>>
>>> If that's not what you are suggesting, do you recommend using the
>>> vendor/branch strategy on a development server and then promoting it to
>>> the
>>> other various environments, including production, by archive/pack, copy to
>>> the target environment(s), and unpacking on the target?
>>>
>>>
>>> J
>>>
>>>
>>>
>

[Jacques Le Roux]

It has been removed from the framework and put in Attic (ie in the repo history)

Jacques

Justin Dagostino wrote:

> Thanks.   Just confirming my assumptions.  I liked the Debian package
> management possibility, but it's been retired (and maybe should be removed
> from the framework).
>
>
> On Wed, Oct 23, 2013 at 5:11 PM, Adrian Crum <
> [hidden email]> wrote:
>
>> If you don't want to use SVN or Ant on your production server, then you
>> have no choice - you must build it somewhere else and then copy it to the
>> production server.
>>
>> Adrian Crum
>> Sandglass Software
>> www.sandglass-software.com
>>
>>
>> On 10/23/2013 2:04 PM, Justin Dagostino wrote:
>>
>>> Thanks again for the reply and the link.   One thing that is not 100%
>>> clear
>>> is whether or not people are actually checking out from SVN (from whatever
>>> branch) directly on production (and possibly running Ant tasks there as
>>> well).  I'd really like to avoid that.
>>>
>>> If that's not what you are suggesting, do you recommend using the
>>> vendor/branch strategy on a development server and then promoting it to
>>> the
>>> other various environments, including production, by archive/pack, copy to
>>> the target environment(s), and unpacking on the target?
>>>
>>>
>>> J