[Collective-checkins] r124640 - collective.developermanual/trunk/source/hosting

[Mikko O. <svn...@pl...>]

Author: miohtama
Date: Tue Aug 31 15:04:34 2010
New Revision: 124640

Modified:
   collective.developermanual/trunk/source/hosting/zope.txt
Log:
export/import notes

Modified: collective.developermanual/trunk/source/hosting/zope.txt
==============================================================================
--- collective.developermanual/trunk/source/hosting/zope.txt	(original)
+++ collective.developermanual/trunk/source/hosting/zope.txt	Tue Aug 31 15:04:34 2010
@@ -103,4 +103,19 @@
 ===============================
 
 In the case you have set virtual hosting rules so that Zope does no longer allow you to access the management interface,
-you can add _SUPPRESS_ACCESSRULE" to the URL to disable VirtualHostMonster.
\ No newline at end of file
+you can add _SUPPRESS_ACCESSRULE" to the URL to disable VirtualHostMonster.
+
+Import and export
+------------------
+
+Zope application server offers copying parts of the tree structure via import/export feature.
+Exported file is basically a Python pickle containing the chosen node and all child nodes.
+
+Importable .zexp files must be placed on ``/parts/instance/import``  buildout folder on the server. 
+If you are using  clustered ZEO set-up, always run imports through a specific front-end instance
+by using direct port access. Note that ``parts`` folder structure is pruned on each
+buildout run.
+
+More information
+
+* http://quintagroup.com/services/support/tutorials/import-export-plone/ 
\ No newline at end of file