Hi Eric, can you expand a bit on the Flex-rep feature? Or point me to the doc? We're using 4.2 for some time now, but I wasn't aware of such a feature.
By the way we're also using XQSync quite happily. cheers, Jakob. On Tue, May 24, 2011 at 17:44, Eric Bloch <[email protected]> wrote: > We use XQSync to push developer.marklogic.com stage->production today. You > can specify database directory URIs (or collections) you want to push but you > have to detect the changes yourself, if you want to push only those > individual pieces. > > We are looking to use the 4.2 Flex-rep feature as an alternative. > > -Eric > > > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Rix, Brad > [[email protected]] > Sent: Tuesday, May 24, 2011 8:05 AM > To: General MarkLogic Developer Discussion > Subject: Re: [MarkLogic Dev General] Pushing documents from development to > production > > One possibility is to use XQSync. > > XQSync is a command-line, Java-based tool, useful for synchronizing MarkLogic > databases to and from other databases, filesystems, and zip-files. To get > started using XQSync, try the tutorial. > > http://developer.marklogic.com/code/xqsync > > It can synchronize the content as well as the properties, permissions, etc > (configurable). > > You run the tool to create a zip file from one system, then use the tool > again to push the zip file to the other system. This may not work well if > you have lots of data (more than a zip file worth). > > Brad Rix > Senior Developer > +1 (303) 542-2172 | Office > +1 (303) 915-2771 | Mobile > [email protected] > http://www.flatironssolutions.com > IM: AIM: BradRix MSN: [email protected] > > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Murray, Gregory > Sent: Tuesday, May 24, 2011 8:30 AM > To: General MarkLogic Developer Discussion > Subject: [MarkLogic Dev General] Pushing documents from development to > production > > Hello, > > We have an instance of MarkLogic Server running on a development machine and > another on a production machine. No doubt such a setup is commonplace. What's > a good way to push documents from the development database to the production > one? The ideal solution would only push documents that contain changes, but > pushing everything would be ok as long as it's not painfully slow. > > Thanks, > Greg > > > Gregory Murray > Digital Library Application Developer > Princeton Theological Seminary > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
