Re: 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]> |
Raphael Ritz wrote: > > Graham Perrin wrote: >> … how should that person plan for an upgrade to 4.x? > > By considering to use > > http://pypi.python.org/pypi/collective.recipe.filestorage > > Raphael > >> 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? > Raphael, thanks, that's an interesting recipe. An underlying question: must a person with multiple Data.fs think about multiple BLOB storages (with or without that recipe) *before* an upgrade from 3.x to 4.x? Put another way: if they upgrade, and over a period of weeks or months the one /blobstorage/ is populated with BLOBs from all sites A, B and C, then eventually they discover collective.recipe.filestorage and decide that separate storages is the way to go, then will Plone: i) intelligently work with the existing mixture of all three, to separate the BLOBs for sites B and C, from the BLOBs for site A or ii) leave the *existing* BLOBs for A, B and C together; and separate only the BLOBs that are added *after* separation has been specified? -- 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--tp4433128p4440282.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