[Checkins] SVN: Sandbox/philikon/zopeproject/trunk/README.txt README for zopeproject (replacing the one from grokproejct that was still in

[Philipp von Weitershausen]

Log message for revision 77968:
  README for zopeproject (replacing the one from grokproejct that was still in 
  there from the copying)
  

Changed:
  U   Sandbox/philikon/zopeproject/trunk/README.txt

-=-
Modified: Sandbox/philikon/zopeproject/trunk/README.txt
===================================================================
--- Sandbox/philikon/zopeproject/trunk/README.txt	2007-07-14 17:41:46 UTC (rev 77967)
+++ Sandbox/philikon/zopeproject/trunk/README.txt	2007-07-14 18:01:58 UTC (rev 77968)
@@ -1,69 +1,64 @@
-grokproject provides an easy way to get started with a `grok
-<http://cheeseshop.python.org/pypi/grok>`_ web application.  Simply
-install ``grokproject``::
+With ``zopeproject`` you can start a new Zope-based web application from
+scratch with just a two commands::
 
-  $ easy_install grokproject
+  $ easy_install zopeproject
+  $ zopeproject MyZopeProj
 
-and run the ``grokproject`` script with the name of the project you'd
-like to create as an argument::
+This will ask you the name and password for an initial administrator
+user.  It will also ask you where to put the Python packages ("eggs")
+that it downloads.  This way multiple projects created with
+``zopeproject`` can share the same packages and won't have to download
+them each time.
 
-  $ grokproject MammothHerd
-  ... many lines of output here
+After asking the questions, ``zopeproject`` will download the
+``zc.buildout`` package that will be used to build the sandbox, unless
+``zc.buildout`` is already installed locally.  Then it will invoke
+``zc.buildout`` to download Zope and its dependecies.  If you're doing
+this for the first time or not sharing packages between different
+projects, this may take a while.
 
-This will not only create a project area for you to work in, it will
-also download and install grok and Zope 3 (the application server grok
-is built on).
+When ``zopeproject`` is done, you will find a typical Python package
+development environment in the ``MyZopeProj`` directory: the package
+itself (``myzopeproj``) and a ``setup.py`` script.  There's also a
+``bin`` directory that contains scripts, such as ``paster`` which can
+be used to start the application::
 
-After the project area has been created successfully, you will find an
-empty Python package in the ``src`` directory in which you can place
-the code for your web application.  To start the Zope server, execute
-``bin/zopectl fg``.
+  $ cd MyZopeProj
+  $ bin/paster serve deploy.ini
 
+
 Changes
 =======
 
-0.5.2 (unreleased)
-------------------
-
-* ...
-
-0.5.1 (2007-07-14)
-------------------
-
-* Use the new 'application' recipe from zc.zope3recipes so that we can
-  get rid of the dead chicken [zope3] section in buildout.cfg.
-
-0.5 (2007-07-14)
+0.3 (2007-07-14)
 ----------------
 
-* The bin/instance script has been renamed to bin/zopectl for better
-  recognizability.
+* Renamed to ``zopeproject``.
 
-* grokproject is much quieter by default (by quieting down
-  PasteScript, easy_install and zc.buildout).  Use the -v option for
-  verbose mode.
+* Incorporated much of the ``grokproject`` 0.5.x infrastructure.  This
+  makes it much more robust, especially when launching zc.buildout.
 
-* Fixed https://bugs.launchpad.net/grok/+bug/119805:
-  A new project created with grokproject can't be called 'grok' or 'zope'.
+* Merged ``make-zope-app`` and ``deploy-zope-app`` back into one
+  command: ``zopeproject``.
 
-* By default, zc.buildout will now be told to place eggs in a
-  user-specified shared eggs directory.  Also, it will not look for
-  newer versions of existing eggs by default.
+0.2 (2007-07-06)
+-----------------
 
-0.4 (2007-07-12)
-----------------
+* Renamed to ``make-zope-app``.
 
-* As grok now depends on Zope 3.4 eggs, use zc.zope3recipes
-  application and instance recipes.
+* Split ``mkzopeapp`` into two commands: ``make-zope-app`` and
+  ``deploy-zope-app``.
 
-* Don't spawn processes to bootstrap and run the buildout.  Instead,
-  try to simply import zc.buildout.  If that doesn't work, call the
-  setuptools API to install it and then simply import it.
+* No longer use ``zope.paste`` for the application factory.  Instead,
+  each application that's created from the skeleton defines its own
+  factory (which is reasonably small and gains flexibility).
 
-* Fixed https://bugs.launchpad.net/grok/+bug/113103:
-  Default index template was missing closing html tag.
+* Get rid of the ``start<<Project>>`` script.  Simply use ``bin/paster
+  serve deploy.ini`` for starting the server.
 
-0.1 thru 0.3
-------------
+* Use the ``Paste#http`` server by default.
 
-Initial development versions, supporting Zope 3.3.
+0.1 (2007-07-XXX)
+-----------------
+
+Initial release as ``mkzopeapp``