Changeset 11949 for main/waeup.kofa/branches/henrik-regista/docs/INSTALL.txt

Timestamp:

13 Nov 2014, 14:40:27 (10 years ago)

Author:

Henrik Bettermann

Message:

Change of name.

File:

• main/waeup.kofa/branches/henrik-regista/docs/INSTALL.txt (modified) (12 diffs)

main/waeup.kofa/branches/henrik-regista/docs/INSTALL.txt

@@ -1 @@
-Installation of Kofa
+Installation of Ikoba
 ####################
 
-These are generic installation instructions for the WAeUP_ ``Kofa``
+These are generic installation instructions for the WAeUP_ ``Ikoba``
 student information portal and customized versions thereof.
 
@@ -19 +19 @@
 *************
 
-The Kofa packages are based on `Grok`_, which is a Python_
+The Ikoba packages are based on `Grok`_, which is a Python_
 framework for agile webapplication development. Grok_ itself is based
 on `Zope`_.
@@ -31 +31 @@
 ====================
 
-For a `Kofa` install we need of course `Python`_ installed as well as
+For a `Ikoba` install we need of course `Python`_ installed as well as
 some standard developer tools like C compilers, C libraries, etc.
 
@@ -69 +69 @@
 where you can run your code without touching any other installations.
 
-`virtualenv`_ is also the only possibility to build a `Kofa` install
+`virtualenv`_ is also the only possibility to build a `Ikoba` install
 without the need of superuser permissions. In short: `virtualenv`_
 will make your life easier. Use it.
@@ -144 +144 @@
 
 Now, as the sandbox is activated (see above, if not), we can fetch the
-sources for Kofa.
-
-As Kofa is currently available from the Subversion_ repository only,
+sources for Ikoba.
+
+As Ikoba is currently available from the Subversion_ repository only,
 we use the Subversion_ client `svn` and checkout the main devel branch
-of the `waeup.kofa` package like this::
-
-  (py27)$ svn co https://svn.waeup.org/repos/main/waeup.kofa/trunk
-
-The command should fetch the Kofa base package sources for you and
+of the `waeup.ikoba` package like this::
+
+  (py27)$ svn co https://svn.waeup.org/repos/main/waeup.ikoba/trunk
+
+The command should fetch the Ikoba base package sources for you and
 will put everything in a new directory ``trunk/``.
 
@@ -161 +161 @@
 and you can start building the real package.
 
-.. note:: If you not want to work with the `waeup.kofa` package but a
+.. note:: If you not want to work with the `waeup.ikoba` package but a
           customized package (like ``waeup.aaue`` or similar), then
           you can use the above checkout command but with
-          ``waeup.kofa`` replaced by the name of the customized
+          ``waeup.ikoba`` replaced by the name of the customized
           package::
 
@@ -200 +200 @@
 ***************************
 
-You can run ``Kofa`` with a single client (useful for evaluation,
+You can run ``Ikoba`` with a single client (useful for evaluation,
 development, etc.) or with multiple clients running in parallel. The
 latter setup is useful in productive environments with many thousands
@@ -243 +243 @@
 You should be able now to start the created instance by doing::
 
-  $ ./bin/kofactl fg
+  $ ./bin/ikobactl fg
 
 Alternatively you can do::
@@ -249 +249 @@
   $ bin/paster serve parts/etc/deploy-themed.ini
 
-The port numbers where Kofa is running on your server are defined in
-`buildout.cfg` under ``[kofa_params]``.
+The port numbers where Ikoba is running on your server are defined in
+`buildout.cfg` under ``[ikoba_params]``.
 
 If you now point a browser to the right port on your server, for example::
@@ -257 +257 @@
 
 you should get a login pop-up, where you can login as superuser with
-``grok`` and ``grok`` as username/password (Kofa base package only!).
+``grok`` and ``grok`` as username/password (Ikoba base package only!).
 
 You can stop the instance by pressing <CTRL-C>.
@@ -298 +298 @@
 ========================
 
-To install Kofa ZEO-based you can run `buildout` with the given
+To install Ikoba ZEO-based you can run `buildout` with the given
 (or your own) configuration file like this::
 
@@ -451 +451 @@
 We need, however, not everything with a ZEO-deploy that is listed in a
 default buildout. We might do not need docs, no profiling, etc. Also a
-regular non-ZEO kofactl might not make to much sense. Therefore all
+regular non-ZEO ikobactl might not make to much sense. Therefore all
 this might be subject to changes.