From: Michael J. <ube...@gm...> - 2022-05-12 18:56:08
|
Hi Florian, Here’s an example of how I do it: https://gist.github.com/ubermichael/beff98fc0b939788c908ac75b149d35c We have one .properties file for each eXistDB instance. The example defaults to using localhost, but using other hosts is quite easy: `ant -Dhost=foo fetch` will download all of the data from the host defined in foo.properties. For your question, the store-reports ant target is probably the closest to what you’re trying to do. Michael > On May 11, 2022, at 12:01 PM, Florian Schmitt <mai...@fl...> wrote: > > Hi Michael, > > thanks a lot, that sounds very interesting! I didn't use ant yet, but i'll give it a try. An example would be great and highly appreciated! > > In the meanwhile, i've tested using curl with HTTP PUT. This seems to work nicely for smaller files, but i encounter problems with bigger XML resources. Thus, ant may be a better solution. > > Florian > > Am 11.05.2022 um 19:13 schrieb Michael Joyce: >> Hello Florian, >> This isn’t quite an answer to your question, but may be of some help. >> We use an ant build.xml file to handle large imports, following the documentation in http://exist-db.org/exist/apps/doc/ant-tasks . That ant script reads a properties file with the credentials and other information. >> I can provide an example for you, if you’d like. >> Michael |