Changeset 11404


Ignore:
Timestamp:
24 Feb 2014, 10:24:45 (11 years ago)
Author:
uli
Message:

Update test and build section of part 1.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.aaua/trunk/INSTALL.txt

    r11402 r11404  
    206206
    207207
    208 Preparing the build
    209 ===================
    210 
    211 In the sources directory (``kofa-trunk/``) you have to prepare the
     208Building the Package
     209====================
     210
     211In the sources directory (``trunk/``) you have to prepare the
    212212project to fetch needed components (eggs), compile C-code parts,
    213 etc. This steip will not touch any external projects::
    214 
    215   (py27)$ python bootstrap.py
    216 
    217 This will generate some directories and the ``buildout`` script in
    218 ``bin/`` for us. This step must be executed only once for each
    219 instance.
    220 
    221 You can now deactivate the sandbox::
    222 
    223   (py27)$ deactivate
    224 
    225 Now we can do the real build by triggering::
    226 
    227   $ bin/buildout
     213etc. This is done by a single command ``buildout``::
     214
     215  $ ./bin/buildout
    228216
    229217If this is your first install of some Grok-related project, this step
     
    232220
    233221This step must be redone whenever you change something in
    234 ``buildout.cfg`` or ``setup.py``.
     222``buildout.cfg``, ``buildout-zeo.cfg``, or ``setup.py``.
    235223
    236224Note that if you have more than one sandbox for a Zope-based web
     
    243231  eggs-directory = /home/bruno/buildout-eggs
    244232
    245 
    246 Start the instance
     233where the given directory should be exist beforehand. All eggs of all
     234`buildout` projects will then be stored in this directory (and not
     235fetched anew if already existing there).
     236
     237
     238Start the Instance
    247239==================
    248240
    249241You should be able now to start the created instance by doing::
    250242
    251   $ bin/zopectl fg
     243  $ ./bin/kofactl fg
    252244
    253245Alternatively you can do::
    254246
    255   $ bin/paster serve parts/etc/deploy.ini
     247  $ bin/paster serve parts/etc/deploy-themed.ini
    256248
    257249The port numbers where Kofa is running on your server are defined in
    258 buildout.cfg under [kofa_params].
    259 
    260 If you now point a browser to the right port on your server, for example ::
     250`buildout.cfg` under ``[kofa_params]``.
     251
     252If you now point a browser to the right port on your server, for example::
    261253
    262254  localhost:8080
     
    274266then visible entry in the list of installed applications.
    275267
    276 Running the tests
     268Running the Tests
    277269=================
    278270
    279 The tests are easily run by executing the test runner that's
    280 installed in the ``bin`` directory::
    281 
    282   $ bin/test
     271All WAeUP_ packages come with comprehensive test suites ensuring the
     272software quality also after changes and updates.
     273
     274The package tests are easily run by executing the test runner
     275from the ``bin`` directory::
     276
     277  $ ./bin/test
     278
     279Use the ``-c`` option to get coloured output. Use the ``--pdb`` option
     280to start the Python_ debugger when a test fails.
    283281
    284282
Note: See TracChangeset for help on using the changeset viewer.