My understanding is that flex rep wasn't specifically designed for this use case, but that it should do just fine.
You can control the replication via APIs that, in theory, we'd call when we want to push. David's actually agreed to help us in his spare cycles put an example of this working into play :) -Eric Eric Bloch Director, Community MarkLogic Corporation desk +1 650 655 2390 | mobile +1 650 339 0376 email [email protected]<mailto:[email protected]> web developer.marklogic.com<http://developer.marklogic.com/> twitter @eedeebee On May 24, 2011, at 11:06 AM, David Lam wrote: On Tue, May 24, 2011 at 8:57 AM, Jakob Fix <[email protected]<mailto:[email protected]>> wrote: 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. Here's the guide.... http://docs.marklogic.com/4.2doc/docapp.xqy#display.xqy?fname=http://pubs/4.2doc/xml/replication/title.xml It seemed to me to be more feature rich than XQSync, For example, flexrep can *immediately* keep two databases in sync as soon as documents are updated or added to one. Plus, you can configure it all within the admin UI (no more looooong java command). -David On Tue, May 24, 2011 at 17:44, Eric Bloch <[email protected]<mailto:[email protected]>> wrote: > We use XQSync to push > developer.marklogic.com<http://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]<mailto:[email protected]> > > [[email protected]<mailto:[email protected]>] > On Behalf Of Rix, Brad > [[email protected]<mailto:[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<tel:%2B1%20%28303%29%20542-2172> | Office > +1 (303) 915-2771<tel:%2B1%20%28303%29%20915-2771> | Mobile > [email protected]<mailto:[email protected]> > http://www.flatironssolutions.com<http://www.flatironssolutions.com/> > IM: AIM: BradRix MSN: [email protected]<mailto:[email protected]> > > > > > -----Original Message----- > From: > [email protected]<mailto:[email protected]> > > [mailto:[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]<mailto:[email protected]> > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected]<mailto:[email protected]> > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ > General mailing list > [email protected]<mailto:[email protected]> > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
