Hi Steven, A few points here.
In Archiva 1.3, all of the metadata is derived from the original artifacts, so you can just copy the filesystem to the other machine and reconfigure the repository to point there. It'll be reconstructed on the first scan, though you'll need to reconfigure the authorization as you've indicated. If you want to copy the configuration, you can paste it from the managed repository section of archiva.xml before starting the server. If you want to copy the user configuration, the only option at the moment is to copy the whole users database. We do have export/import tools for that (documented on the site), but it's for the whole user database so if there's a difference you might be looking for something smaller. As long as you have the repository scanning enabled, you can keep them in sync using rsync or similar. Is that what you were looking for? - Brett On 11/11/2010, at 2:07 AM, Steven Siebert wrote: > Hello all, > > I was looking through available documentation and haven't found an elegant > solution yet to allow me to export/import a specific repository. > > My situation is basically that I want to have multiple offline instances of > Archiva and a single Internet-facing one. The Internet-facing instance will > have a specific repository that will house bundles that have passed the QA > process for including in our stable builds. I wish to export this > repository and make it available on the additional offline instances. > Further, all of these offline instances will contain its own repository > specific for its enclave. In at least one situation, one of these > repositories must also be exported and imported on another of the standalone > instances. > > Is there a preferred way to export a specific repository (the artifacts and > preferably the metadata - optionally the user data) and import it into > another Archiva instance? > > Thanks, > > Steve -- Brett Porter [email protected] http://brettporter.wordpress.com/
