EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #00539
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: 10_core.pl regeneration. HElP
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: 10_core.pl regeneration. HElP
- From: Tim Brody <tdb2@ecs.soton.ac.uk>
- Date: Fri, 11 May 2012 10:49:37 +0100
On Tue, 2012-05-08 at 15:32 -0600, ERI UB Belize wrote: > hi, > I am testing out a backup method if eprints ever went down or files > got corrupted. > I want to copy over the version from the production server to a test > server. Thereafter, I would have to modify the DNS entry. > I was reading that this is done through the 10_core.pl > Do I edit this file directly? > In addition, in the 10_core.pl file it states: > This file was created by bin/epadmin > # You can regenerate this file by doing ./bin/epadmin config_core eriubpubs > > Where do I run those regeneration commands? > What all would I have to edit so the test version and the production > version would be accessed from different URL's? You run that on the command line (as you did originally to create the repository). But if you are setting up a test server the best thing to do is to add a file "11_test_core.pl" that overrides the hostname in 10_core. Lastly, you will need to remove your static files to get rid of stale links in HTML pages (archives/[archiveid]/html/*) and do ./bin/generate_apacheconf --replace. -- All the best, Tim
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- [EP-tech] 10_core.pl regeneration. HElP
- From: ERI UB Belize <eriubrepository.bz@gmail.com>
- [EP-tech] 10_core.pl regeneration. HElP
- Prev by Date: [EP-tech] Re: EPC:Print Contributors
- Next by Date: [EP-tech] Re: OAI-PMH export data
- Previous by thread: [EP-tech] 10_core.pl regeneration. HElP
- Next by thread: [EP-tech] EP3.2 bugfix: datetime search with seconds and OAI date granularity YYYY-MM-DDThh:mm:ssZ
- Index(es):