From:eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andrew Beeken
Sent: 25 April 2016 14:20
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Copy live EPrints to staging server

From:eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Adam Field
Sent: 25 April 2016 13:43
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Copy live EPrints to staging server

1) install a fresh copy of EPrints and configure it to work on the dev server (to make sure all prerequisites are ship-shape).  It'll make things simpler if you use the same database name, username and password as the live repository.  Test that you can raise it in a browser, log in, create a record, etc.  There's a training video for this.

2) Dump the live database into the EPrint tree somewhere (perhaps <eprints_root>/archives/<foo>/db_dump/<timestamped_filename>.mysqldump)

3) Create an tarball of the EPrints tree (tar cvzf live_eprints<datestamp>.tar.gz <eprints_root>)

4) Copy the tarball to dev

5) tar xvzf the file to somewhere appropriate, check file permissions for the apache user on dev

6) undump the database dump (cat filename | mysql -u username -p) -- easy if you have used the same username and password as all the permissions are set up.  Still easy if you didn't and know how to create users and set permissions in mysql.

7) edit the 10_core.pl file in the archive directory to use the URL of the dev server.  Then run generate apacheconf (I think with the --replace flag, but that's from memory).

8) Change your apache configuration to point to where you unpacked the eprint tree.

9) restart apache.

10) Debug the above process and document it on the wiki.

11) Think about getting your repository into source control to make this easier.

Hi folks,

I’m trying to bring our live EPrints install over to a staging server to do some work on it, but I’m struggling to do this in an elegant way. What’s the best approach? I tried bringing the archive files down and repopulating the database; there are also a few core changes to our install in Perl-Lib which need bringing down however most times I pull all these across and restart apache it screws things over. I’m pretty sure I need to tweak some config settings and possibly run a few things from the command line but I was wondering if anyone could digest the procedure for me or point me in the direction of one if it’s already been written!

Cheers!

Andrew