Changeset 11402 for main/waeup.aaua

Timestamp:

24 Feb 2014, 09:51:06 (11 years ago)

Author:

uli

Message:

Add bootstrapping section.

File:

• main/waeup.aaua/trunk/INSTALL.txt (modified) (5 diffs)

main/waeup.aaua/trunk/INSTALL.txt

@@ -94 +94 @@
 
 
-Creating a sandbox
+Creating a Sandbox
 ==================
 
@@ -138 +138 @@
 
 
-Get the Sources, Luke
-=====================
+Getting the Sources
+===================
 
 Now, as the sandbox is activated (see above, if not), we can fetch the
@@ -171 +171 @@
 
 
+Bootstrapping the Build
+=======================
+
+After `Creating a Sandbox`_ and `Getting the Sources`_ we have to
+initialize the newly created development environment::
+
+  (py27)$ python bootstrap.py
+
+This should create a local ``bin/`` directory with at least a script
+``buildout`` in it.
+
+If bootstrapping fails, chances are, that you need the `distribute`
+package installed. In a virtual environment you can install it without
+interfering with other packages installed on your server:
+
+  (py27)$ pip install --upgrade distribute
+
+Afterwards you have to retry the bootstrapping, until you get a
+working ``buildout`` script in the local ``bin/`` directory.
+
+Once the ``buildout`` script exists, you do not have to activate the
+virtual envronment any more (although you can).
+
+
 Part 1: Single Client Setup
 ***************************
@@ -177 +201 @@
 development, etc.) or with multiple clients running in parallel. The
 latter setup is useful in productive environments with many thousands
-users. We will cover both setup types. The first is covered here, the
-latter one is covered in Part 2.
+users and called a ``ZEO`` install. We will cover both setup
+types. The first is covered here, the latter one is covered in `Part
+2: ZEO Install`_.
+
 
 Preparing the build
@@ -257 +283 @@
 
 
-Part 2: Deploying Kofa as ZEO install
-*************************************
+Part 2: ZEO Install
+*******************
 
 Each ZEO install consists of at least one ZEO server and normally two