Hi. I was wondering if somebody has experience with ex- and importing large amounts of data. While doing the ex- or import Magnolia will break and the only workaround is to export subfolder by subfolder. Is the Magnolia Packager able to handle large amounts of data? I was once able to export part of the data and it's already 50MB so I think the whole folder I want to export would be about 100 - 200 MB.
Regards Jan Magnolia - User mailing list wrote: > > Hi Ben, > > just send me an email (ralf at hirning.de) and you can get a 1 month test > license (full functionality, but you are not entitled to use it for > production). > > I am using Magnolia Packager on my Magnolia 2.1.5 sites for deploying > change > requests and for backup. Originally I created Magnolia Packager for > Magnolia > 2.1.5. So all the features are available, but the user interface is a > little > bit different. > > The idea behind Magnolia Packager is that you can bundle packages with > whatever you need for your Magnolia project. > > For illustration let us look at an example using two packages: > 1. The definition of the package for all my templates (and paragraphs) > > + config repository: /modules/templating/Paragraphs/rhg > + config repository: /modules/templating/Templates/rhg > + config repository: /modules/templating/dialogs/paragraphs/rhg > + config repository: /modules/templating/dialogs/templates/rhg > + web application: /docroot/rhg > + web application: /paragraphs/jsp/rhg > + web application: /templates/jsp/rhg > > 2. The definition of the package for a site's content: > > + website repository: /site > > Two examples what you can do with these two packages: > > 1. Clone the site: > - setup a blank Magnolia instance (including Magnolia Packager) > - upload and install template package > - upload and install content package > - restart the instance > > 2. Deploying change requests: > - make your changes on your dev environment (I use Magnolia integrated > in Eclipse) > - backup (download) the templating package from your dev environment > - upload and install the templating package to your instances > according your deployment process: > -- test environment to test your changes > -- production environment > > Ralf > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 29. August 2006 18:08 > An: [email protected] > Betreff: [magnolia-user] Magnolia Packager and Magnolia 2.1.5 > > I'm about to purchase Magnolia Packager. Before doing so, can someone > confirm from personal experience that this will give me a programmatic > approach to releasing config nodes in Magnolia 2.1.5? I do not intend to > upgrade to 3.0 at this time. (Long story short, I want to avoid the > manual process of releasing configs and have them go out with the rest > of template code in svn.) > > If Dr. Hirning is listening, I'd love to hear from you. > > Thanks, > > Ben Brock > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > > -- View this message in context: http://www.nabble.com/AW%3A--magnolia-user--Magnolia-Packager-and-Magnolia-2.1.5-tf2187581.html#a10798867 Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
