Helix84,
        Don't think I made myself clear, each server will have its own 
dspace.cfg setup for the initial deployment and then the rsync should just copy 
over what has changed in the core API and modules but not the config etc.
        This will work will it not?

Regards,
        Ben

------------------------------------------------------------------
Dr Ben Ryan
Jorum Technical Coordinator (Services)

5.13 Roscoe Building
The University of Manchester
Oxford Road
Manchester
M13 9PL
Tel: 0160 275 6256
E-mail: benjamin.r...@manchester.ac.uk
------------------------------------------------------------------


-----Original Message-----
From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84
Sent: 18 September 2012 11:58
To: Benjamin Ryan
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Best (good) practice for building/deploying DSpace

On Tue, Sep 18, 2012 at 12:51 PM, Benjamin Ryan 
<benjamin.r...@manchester.ac.uk> wrote:
>         Thanks I will take a look at lsyncd.

That was just an example, you may want to search for similiar options in your 
distribution's repository.

>         One other question: I will have configs for both the live and staging 
> servers and I assume that once I have setup the DSpace install on both 
> machines (via ant) I can just use rsync when I need to update the codebase 
> after a new build?

Not at the moment, because dspace.cfg contains hostname and url, but this 
should be possible in 3.0 thanks to DS-1208 [1], which lets you keep some 
hosts-specific setting in a machine-local build.properties file and fill them 
into dspace.cfg at ant update time.

[1] https://jira.duraspace.org/browse/DS-1208

Regards,
~~helix84
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to