Metadata-Version: 1.0
Name: repoze.plone
Version: 3.1.1.2
Summary: A metapackage that allows installation of Plone 3.1.1within a repoze environment
Home-page: http://www.repoze.org
Author: Agendaless Consulting
Author-email: reopze-dev@lists.repoze.org
License: BSD-derived (http://www.repoze.org/LICENSE.txt)
Description: Overview
        
        repoze.plone is a mechanism that allows you to easy install and run
        the Plone 3 application server via the repoze deployment stack.
        
        Installing
        
        With a Python 2.4 interpreter >= 2.4.3 (**Python 2.5+ is
        unsupported**) with setuptools installed, install the 'virtualenv'
        package::
        
        $PYTHONHOME/bin/easy_install virtualenv
        
        When this is done, create a virtualenv "sandbox" to hold the
        repoze.zope2 packages and instance data:
        
        $PYTHONHOME/bin/virtualenv --no-site-packages /path/to/sandbox
        
        A directory named 'sandbox' will be created in the /path/to.
        directory.  You can use any path you like.
        
        After creating a virtualenv sandbox, install the 'repoze.plone' egg
        into the virtualenv.
        
        /path/to/sandbox/bin/easy_install -i http://dist.repoze.org/simple repoze.plone
        
        NOTE: Some "Syntax Error" messages may be printed to the console
        during this process; these can be ignored.  This is distutils
        attempting to byte-compile Zope "Python Scripts" in skin directories
        that aren't valid Python syntax.
        
        After the repoze.zope2 packages are installed into the virtualenv,
        you can finally create "instance" files (config files) within the
        sandbox by running "mk2zope2instance"::
        
        /path/to/sandbox/bin/mkzope2instance .
        
        After these steps have been performed, here's what has happened::
        
        - a "virtual Python" has been installed within the
        "/path/to/sandbox" directory.  Packages installed to this virtual
        Python's 'site-packages' directory will not conflict with packages
        installed into your "normal" Python's 'site-packages' directory.
        
        - All packages required by repoze.zope2 have beeen downloaded,
        compiled, and installed as Python eggs in the *virtual* Python's
        'site-packages' directory.
        
        - 'Products', 'logs', 'var', and 'etc' directories have been created
        inside the sandbox directory.  'Products' is where 3rd party Zope
        products should be installed.  'logs' is where Zope logs will go,
        'var' is where ZODB data files will go, 'etc' is where config
        files are placed.
        
        - A sample set of configuration files have been installed into the
        sandbox directory's 'etc' subdirectory.  These include::
        
        - 'zope.ini', a Paste configuration file used to establish the
        Paste (WSGI) pipeline which repoze.zope2 will use to serve up
        repoze.zope2.
        
        - 'zope.conf', a classic Zope 2 configuration file which can be
        used to adjust Zope settings.
        
        - 'site.zcml', a boilerplate site.zcml that should be used to
        control ZCML processing.
        
        Utilities
        
        These utilities are available in the "bin/" directory of the
        generated sandbox.
        
        installproduct -- provided the directory path of a classic Zope 2
        Product (unpacked), installproduct will attempt to convert the
        product into a Python egg and install it into the sandbox's
        site-packages directory.  This is an alternative to unpacking
        putting the product inside the sandbox "Products" directory.
        
        addzope2user -- script which adds a management user to the Zope root
        user folder.
        
        runzope2script -- script which runs a Python script with the root
        Zope application object as the "app" object in the globals
        namespace.
        
        debugzope2 -- runs the Python interactive interpreter with the Zope
        root object bound to the "app" name in the global dictionary/
        
        mkzope2instance -- create zope2 instance files in a directory.
        
        Starting
        
        To start the Zope server on port 8080, cd to the sandbox directory
        you created via "setup.py sandbox" and run::
        
        bin/paster serve etc/zope2.ini
        
        When you visit http://localhost:8080/ in a browser, you should see
        the Zope 2 quickstart page.
        
        To manage the resulting Zope 2 site, you'll need to add a
        management user.  From the sandbox directory, run::
        
        bin/zope2adduser <username> <password>
        
        Once this is done, you should be able to visit
        http://localhost:8080/manage and log in with the username and
        password you supplied.
        
        Creating a Plone Site
        
        Add a "Plone Site" using the ZMI dropdown "add" menu.
        
Keywords: web application server wsgi zope plone
Platform: UNKNOWN
Classifier: Development Status :: 1 - Planning
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Framework :: Plone
Classifier: Topic :: Internet :: WWW/HTTP
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
Classifier: Topic :: Internet :: WWW/HTTP :: WSGI
Classifier: Topic :: Internet :: WWW/HTTP :: WSGI :: Application