|
Revision 11, 1.5 kB
(checked in by mauro, 9 months ago)
|
--
|
| Line | |
|---|
| 1 |
Requirements: |
|---|
| 2 |
============= |
|---|
| 3 |
|
|---|
| 4 |
1. PIL (aka python-imaging in most unix systems). |
|---|
| 5 |
|
|---|
| 6 |
2. python development files (it could be python-dev in unix systems). |
|---|
| 7 |
|
|---|
| 8 |
3. gcc and usual tools for compiling and installing. |
|---|
| 9 |
|
|---|
| 10 |
|
|---|
| 11 |
Installing a BioPlone site: |
|---|
| 12 |
=========================== |
|---|
| 13 |
|
|---|
| 14 |
1. Run bootstrap.py with the python interpreter you want to use. This |
|---|
| 15 |
will install Buildout. |
|---|
| 16 |
|
|---|
| 17 |
$ python2.4 bootstrap.py |
|---|
| 18 |
|
|---|
| 19 |
or if you've used MacPorts for MacOSX to install your python 2.4: |
|---|
| 20 |
|
|---|
| 21 |
$ /opt/local/bin/python2.4 bootstrap.py |
|---|
| 22 |
|
|---|
| 23 |
or if you've used Fink for MacOSX to install your python 2.4: |
|---|
| 24 |
|
|---|
| 25 |
$ /sw/bin/python2.4 bootstrap.py |
|---|
| 26 |
|
|---|
| 27 |
2. Edit the newly created buildout.cfg to select the profile you want to |
|---|
| 28 |
use; production, staging or development. For example: |
|---|
| 29 |
|
|---|
| 30 |
[buildout] |
|---|
| 31 |
extends = profiles/development.cfg |
|---|
| 32 |
|
|---|
| 33 |
note: If you intend to run the development profile you don't need to |
|---|
| 34 |
change anything here. |
|---|
| 35 |
|
|---|
| 36 |
3. Run buildout |
|---|
| 37 |
|
|---|
| 38 |
$ bin/buildout -v |
|---|
| 39 |
|
|---|
| 40 |
note: it may take some time ... |
|---|
| 41 |
|
|---|
| 42 |
4. Start up the instance |
|---|
| 43 |
|
|---|
| 44 |
$ bin/instance fg |
|---|
| 45 |
|
|---|
| 46 |
5. Log into the ZMI at http://localhost:8080/manage as (admin/admin). |
|---|
| 47 |
Create a Plone site and then go to the quickinstaller and install the |
|---|
| 48 |
following products: |
|---|
| 49 |
|
|---|
| 50 |
plone4bio.base |
|---|
| 51 |
plone4bio.pscoils |
|---|
| 52 |
|
|---|
| 53 |
Now you should be able to add new Sequence types to your Plone site and |
|---|
| 54 |
to run the pscoils (http://www.plone4bio.org/pscoils/) code |
|---|
| 55 |
against it. |
|---|
| 56 |
|
|---|
| 57 |
6. To extend the BioPlone site with new predictors, refer to the |
|---|
| 58 |
skeleton code in plone4bio.pscoils: you should be able to create a set |
|---|
| 59 |
of tools to run against your sequences. |
|---|