Where there is more than one var/Data.fs in Plone 3.x: how to plan for more than one var/blobstorage before an upgrade to 4.x?
Graham Perrin <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Cc: [email protected] (with apologies for cross-posting) Reading <http://manage.plone.org/documentation/kb/multiple-plone-sites-per-zope-instance-using-separate-data-fs-files-for-each-one> alongside <http://manage.plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0> (some of which is not yet published): If an administrator has designed their Plone 3.x installation to have more than one Data.fs (say, one per site), then how should that person plan for an upgrade to 4.x? Would it be essential for their buildout for 4.x to create separate BLOB storages *before* the upgrade? Or could they upgrade first — to just one var/blobstorage for all sites — then think about separation at some point in the future? -- View this message in context: http://n2.nabble.com/Where-there-is-more-than-one-var-Data-fs-in-Plone-3-x-how-to-plan-for-more-than-one-var-blobstorage--tp4433128p4433128.html Sent from the Documentation Team mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs