On Fri, Oct 12, 2012 at 4:14 PM, Darren Arsenault <[email protected]> wrote: > There is no data to worry about, so it seems as simple as dropping/recreating > the database, deleting the [dspace] and [dspace-source] directories of the > 1.7.2 instance, and then installing the new instance.
Sounds right. You may also have something left in the Tomcat configuration that normally doesn't change one DSpace version to the next, but you will want to match that with your production server, too (server.xml and/or $CATALINA_HOME/conf/Catalina/localhost/*). Make sure to match the versions of all dependencies: https://wiki.duraspace.org/display/DSDOC18/Installation#Installation-PrerequisiteSoftware If fact, I wouldn't bother with doing all that. Why not just dump the disk image to the other server, change network and hostname settings and be sure you have a 1:1 copy? Even easier to do that if it's a VM. Regards, ~~helix84 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
