1)       Log into your repository and uninstall any bazaar packages you’ve installed.  Check the database.pl configuration file in the cfg.d directory to find out the database name, then drop that database.  Then delete the <eprints_root>/archives/<archive_id> directory.  Run generate_apacheconf with the --replace flag then restart apache.  I think that’ll take care of it

2)       Yes.  First stop people logging in.  Just add ‘return 0;’ to the top of the check_user_password function at the top of the user_login.pl file in cfg.d then restart the webserver.  You’ll need to also check the loginticket table in the database – feel free do delete every row from it.  You may want to put a warning message on the login page so that people don’t think they’re getting their passwords wrong.

--

Adam

Bump on this too J

Hello all!

Just a couple of questions that will help me in my migration:

·         Is there a command line input to completely tear down an instance of EPrints? Looking at the wiki there should be a “delete” command but this no longer seems to work? Ideally I’d like to be able to build a repository, test some things and then remove the repository and all associated files to start again, making this an iterative process.

·         Is there a way to “lock down” a repository to stop users being able to add records? I’m thinking for when we’re in the final processes of migrating the data across, I want to be able to put the live repository effectively in stasis – can I do this with a config flag somewhere?

Thanks in advance!

Andrew

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/