Hey, all.
In the past my git-based DSpace workflow was this: our DSpace git
repository had 'development' and 'production' branches, and I maintained
two config files, dev_dspace.cfg and prod_dspace.cfg. When redeploying
my web apps I simply specified which config I want to use, for example:
On Fri, Jun 8, 2012 at 1:23 PM, Alan Orth alan.o...@gmail.com wrote:
How are other people handling this?
I'm sorry if my simple answer will let you down, but I manually copy
over a config directory with local customizations after each ant
update. This directory contains only the files that are
On Fri, Jun 8, 2012 at 2:44 PM, Alan Orth alan.o...@gmail.com wrote:
Helix,
Yeah, I could do that. Maybe something something like dev_modules and
prod_modules.
I wonder how hard it would be to add an option ant's build script which
allowed for the specification of a custom modules
Helix,
Oops, thanks for CC'ing the list.
I'm a rubbish programmer, but I might take a look at this kind of
functionality. Or maybe Tim/Peter/etc might decide this feature is
really useful and take it up on their own ;).
Alan
On 06/08/2012 03:49 PM, helix84 wrote:
On Fri, Jun 8, 2012 at
4 matches
Mail list logo
