Changeset 11404
- Timestamp:
- 24 Feb 2014, 10:24:45 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.aaua/trunk/INSTALL.txt
r11402 r11404 206 206 207 207 208 Preparing the build 209 =================== 210 211 In the sources directory (`` kofa-trunk/``) you have to prepare the208 Building the Package 209 ==================== 210 211 In the sources directory (``trunk/``) you have to prepare the 212 212 project 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 213 etc. This is done by a single command ``buildout``:: 214 215 $ ./bin/buildout 228 216 229 217 If this is your first install of some Grok-related project, this step … … 232 220 233 221 This step must be redone whenever you change something in 234 ``buildout.cfg`` or ``setup.py``.222 ``buildout.cfg``, ``buildout-zeo.cfg``, or ``setup.py``. 235 223 236 224 Note that if you have more than one sandbox for a Zope-based web … … 243 231 eggs-directory = /home/bruno/buildout-eggs 244 232 245 246 Start the instance 233 where the given directory should be exist beforehand. All eggs of all 234 `buildout` projects will then be stored in this directory (and not 235 fetched anew if already existing there). 236 237 238 Start the Instance 247 239 ================== 248 240 249 241 You should be able now to start the created instance by doing:: 250 242 251 $ bin/zopectl fg243 $ ./bin/kofactl fg 252 244 253 245 Alternatively you can do:: 254 246 255 $ bin/paster serve parts/etc/deploy .ini247 $ bin/paster serve parts/etc/deploy-themed.ini 256 248 257 249 The 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 252 If you now point a browser to the right port on your server, for example:: 261 253 262 254 localhost:8080 … … 274 266 then visible entry in the list of installed applications. 275 267 276 Running the tests268 Running the Tests 277 269 ================= 278 270 279 The tests are easily run by executing the test runner that's 280 installed in the ``bin`` directory:: 281 282 $ bin/test 271 All WAeUP_ packages come with comprehensive test suites ensuring the 272 software quality also after changes and updates. 273 274 The package tests are easily run by executing the test runner 275 from the ``bin`` directory:: 276 277 $ ./bin/test 278 279 Use the ``-c`` option to get coloured output. Use the ``--pdb`` option 280 to start the Python_ debugger when a test fails. 283 281 284 282
Note: See TracChangeset for help on using the changeset viewer.