On Dec 14, 2010, at 3:11 PM, Ernst Bunders wrote: > > > 2010/12/14 Jan Haderka <[email protected]> > > ok, that I didn't know. We dont use the backup module. To eradicate > cunfusion: The backup module is not the same as what you get when you click > 'backup' in the tools menu?
The backup module provides functionality to backup which is exposed via Tools/backup menu. But the jar itself contains other classes that can be used, like the XmlFileSplitter. > The way we do it now we have two procedures: > - we use a shared dev database, and every week we run a script that creates a > whole bunch of bootstrap files for all our modules. This script overwrites > these files in your local checkout, so after running the script I commit the > new bootstrap data, rebuild the app in our hudson server, and redeploy to test > - When we migrate an existing site to magnolia, I create an import script, > that recreates all the old pages in magnolia. This data (can be quite a lot: > about 10.000 pages for our last product) This data I manually export from > admin central into a number of xml files, which I then manually import in our > test/acceptance/production environments. Not entirely smooth, but a lot of > control. > > In this process i ended up with an xml file that was too big to import, and > subsequently wrote a script to split it up, which woks. But I am not aware of > the standard bootstrap code ordering bootstrap files in a certain way, if all > files in a bootstrap directory are imported. So I import them one by one, to > make sure it goes well. > > So it seems there is more tooling available than I am aware of. I'll have to > check it out. for my clarity: > - The EE export module can create multiple files of a peace of repositpry? Nope, the export will create single file. You can use the XmlFileSplitter to make it into smaller chunks when needed. > - magnolia will bootstrap them in the right order if you put them all in a > bootstrap folder? Unless there is a bug, Magnolia should bootstrap files split with the XmlFileSplitter in the right order. > - there is another way of bootstrapping these files then > 1) do it manually in admin central > 2) put them in the bootstrap dir and let magnolia rebuild the workspace? 3) use the scripts attached to a wiki page (just specify the directory where all files are and let magnolia import it) 4) - variation of 1) - invoke same command via curl or some other cmd line tool. HTH, Jan > > Cheers! > > Ernst > > > If there is any issue then it should indeed get fixed. > > Cheers, > Jan > > >> That's a serious impediment for us. I guess it would not be too much work to >> incorporate this feature in the bootstrap process, perhaps in the EE version? >> >> regards, >> >> Ernst >> >> 2010/12/14 Jan Haderka <[email protected]> >> >> Currently working on finalizing the ModeShape bundle. I'll try to include >> some tests in this setup as well and see how MS deals with the problem ... >> will keep you posted. >> >> Jan >> >> On Dec 14, 2010, at 11:45 AM, Ernst Bunders wrote: >> >> > Well, thanks guys. So I reckon we will have to take the limitations of the >> > (jackrabbit) repository as a given, deplorable as they may be. I must say >> > that although I understand the need to do all this checking on the part of >> > the jcr, >> > >> > - a 2,5+ Gb object tree to represent <300Mb of xml data is a truly lousy >> > ration in terms of efficiency. >> > - There should not be an need to process all this data in memory. It would >> > seem obvious to me that if you design a system for storing data, >> > scalability should be first and foremost on your mind. >> > >> > But: I will put my mutterings aside, face the facts and start thinking >> > about how splitting of xml files will be a part of our workflow in the >> > future. >> > >> > thanks again for the info. >> > >> > regards, >> > >> > Ernst >> > >> > >> >> >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> >> >> >> >> -- >> Ernst Bunders >> Ontwikkelaar VPRO > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > > -- > Ernst Bunders > Ontwikkelaar VPRO ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
