source: main/waeup.sirp/trunk/README.txt @ 5386

Last change on this file since 5386 was 5329, checked in by uli, 14 years ago

Update README.

File size: 2.6 KB
Line 
1waeup.sirp
2**********
3
4The WAeUP Student Information and Registration Portal. `waeup.sirp` is
5a web-based management tool for managing universities and schools.
6
7What is ``waeup.sirp``?
8=======================
9
10The package was created as an effort of the WAeUP group. See
11http://www.waeup.org to learn more about WAeUP.
12
13
14Installation
15============
16
17.. note:: ``waeup.sirp`` might not work with Python > 2.5
18          currently. Use of Python 2.5 is recommended.
19
20.. note:: ``waeup.sirp`` does not work on Windows.
21
22Prerequisites
23-------------
24
25The ``waeup.sirp`` package is based on `Grok`_, which is a Python
26framework for agile webapplication development. Grok itself is based
27on `Zope`_.
28
29.. _Grok: http://grok.zope.org/
30
31.. _Zope: http://www.zope.org/
32
33Both, Grok and Zope, are written in Python (with parts written in
34C). You therefore need `Python`_ installed.
35
36.. _Python: http://www.python.org/
37
38Note, that you also need the Python header files and a compiler to
39compile the parts written in C.
40
41To deploy ``waeup.sirp`` most easily, we use `zc.buildout`_
42
43.. _zc.buildout: http://cheeseshop.python.org/pypi/zc.buildout
44
45You may have setuptools already installed for your system Python. In
46that case, you may need to upgrade it first because buildout requires
47a very recent version::
48
49    $ sudo easy_install -U setuptools
50
51If this command fails because easy_install is not available, there is
52a good chance you do not have setuptools available for your system
53Python. If so, there is no problem because setuptools will be
54installed locally by buildout.
55
56Bootstrap the buildout environment::
57
58    $ python2.5 bootstrap/bootstrap.py
59
60and run the buildout command::
61
62    $ bin/buildout
63    [lots of stuff will be downloaded and installed here]
64
65Note that if you have more than one sandbox for a Zope-based web
66application, it will probably make sense to share the eggs between the
67different sandboxes.  You can tell ``zc.buildout`` to use a central
68eggs directory by creating ``~/.buildout/default.cfg`` with the
69following contents::
70
71    [buildout]
72    eggs-directory = /home/bruno/buildout-eggs
73
74Running the ``waeup`` application
75---------------------------------
76
77You can start Zope with the with the following command:
78
79    $ bin/zopectl fg
80
81If you now connect to port 8080 and log in with username 'grok',
82password 'grok', you should be able to add the grok-based applications
83(such as ``University``) from the menu.
84
85Add an instance of ``University`` and click on the link next to the
86then visible entry in the list of installed applications.
87
88Running the tests
89-----------------
90
91The tests are easily run by executing the test runner that's
92installed in the ``bin`` directory::
93
94    $ bin/test
95
Note: See TracBrowser for help on using the repository browser.