forked from bireme/scielobooks
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME.txt
228 lines (140 loc) · 10.1 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
=====================================
How to install a SciELOBooks instance
=====================================
Install pre-requisites
----------------------
Before installing the SciELO-Books application, install the software listed below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Server software
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
|**software** |**product URL** |**installation method** |**Ubuntu Package name** |
+=====================================+===================================+=========================+==========================+
| Python 2.7 | http://www.python.org/ | OS package manager | python2.7 |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| python2.7 | http://www.python.org/ | OS package manager | python2.7-dev |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| GNU compiler and tools | http://www.python.org/ | OS package manager | build-essential |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| Apache HTTP server 2.2 | http://httpd.apache.org/ | OS package manager | apache2 |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| mod_wsgi - Python adapter(optional) | http://code.google.com/p/modwsgi/ | OS package manager | libapache2-mod-wsgi |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| CouchDB 1.0 | http://couchdb.apache.org/ | OS package manager | couchdb |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| PostgreSQL | http://www.postgresql.org/ | OS package manager | postgresql |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| GIT | http://git-scm.com/ | OS package manager | git-core |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
| Subversion | http://subversion.apache.org/ | OS package manager | subversion |
+-------------------------------------+-----------------------------------+-------------------------+--------------------------+
1. Install each package below using the recommended installation method above.
Note: Python comes pre-installed in most Linux distributions. If Python 2.5 or 2.6 is already installed, there is no need to install a newer version.
Note2: on Ubuntu 10.04 (Lucid) build-essential includes: dpkg-dev, g++, libc6-dev and make
System-wide Python libraries
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------+-------------------------------------------+------------------------------------------------------------------+
|**software** |**product URL** |**installation method** |
+===================+===========================================+==================================================================+
| distribute 0.6.10 | http://pypi.python.org/pypi/distribute | sudo python distribute_setup.py |
+-------------------+-------------------------------------------+------------------------------------------------------------------+
| virtualenv | http://pypi.python.org/pypi/virtualenv | sudo easy_install virtualenv |
+-------------------+-------------------------------------------+------------------------------------------------------------------+
| python gfx module | http://www.swftools.org/gfx_tutorial.html | installation instruction topic 1.1 Compiling gfx and installing |
+-------------------+-------------------------------------------+------------------------------------------------------------------+
2. Download the distribute_setup.py script and use the installed Python interperter to run it as root (this provides the easy_install utility)::
# wget http://python-distribute.org/distribute_setup.py
# python distribute_setup.py
3. Use easy_install to download and install virtuaenv::
# easy_install virtualenv
Configure the database
----------------------
4. Create a `scielobooks_1a` database. The user name and password will not be configured at this time.
Log in to the Futon's web interface::
http://localhost:5984/_utils/
Install the application environment
-----------------------------------
**Note: all of the remainig steps can be performed by a regular user without root access.**
5. Use virtualenv to create an application environment and activate it::
$ virtualenv --distribute --no-site-packages scielobooks-env
$ source scielobooks-env/bin/activate
(scielobooks-env)$ # note that the shell prompt displays the active virtual environment
Install the scielobooks application
-----------------------------------
6. Go to a suitable installation directory and check out the application source::
Development(Recommended):
Read-only:
(scielobooks-env)$ git clone git://github.com/bireme/scielobooks.git
Read+write:
(scielobooks-env)$ git clone [email protected]:bireme/scielobooks.git
Development:
(scielobooks-env)$ svn co http://svn.reddes.bvsalud.org/scielo-books/trunk/scielobooks
Stable:
(scielobooks-env)$ svn co http://svn.reddes.bvsalud.org/scielo-books/tags/<VERSION>
user: anonymous
password: 4guests@
7. With the `scielobooks-env` environment active, use `setuptools` to automagically download and install all the dependencies::
(scielobooks-env)$ python setup.py install
8. Run automated tests (NOT WORKING)::
(scielobooks-env)$ python setup.py test -q
Running the application
-----------------------
Paster
~~~~~~
The Pyramid web framework already comes with Paster. So, in order to run it you simply need to:
1. Create a paster .ini configuration file::
Development:
$ cp development-TEMPLATE.ini development.ini
Production:
$ cp production-TEMPLATE.ini production.ini
Note: The application comes with 2 base templates, for development and for production environments.
See http://pythonpaste.org/script/#configuration for more information about PasteScript.
2. Run::
$ paster serve production.ini --daemon
Apache with mod_wsgi
~~~~~~~~~~~~~~~~~~~~
1. Create and configure a paster .ini configuration file.
Note: The application comes with 2 base templates, for development and for production environments.
Development::
$ cp development-TEMPLATE.ini development.ini
Production::
$ cp production-TEMPLATE.ini production.ini
See http://pythonpaste.org/script/#configuration for more information about PasteScript.
2. Create and configure a .wsgi configuration file.
Note: The application comes with a directory named *apache*, containing templates for deployments using Apache with mod_wsgi
Development::
$ cp apache/app/devel-TEMPLATE.wsgi apache/app/devel.wsgi
Production::
$ cp apache/app/production-TEMPLATE.wsgi apache/app/production.wsgi
Note: The .wsgi configuration file must be configured to point to the previously created .ini file, to match the application's entry point.
3. Configure the Apache WebServer
Note: The application comes with 2 virtual hosts base templates. You can simply create a symlink to the apache's available sites.
Development::
$ cp apache/httpd-devel-TEMPLATE.conf apache/httpd-devel.conf
Production::
$ cp apache/httpd-TEMPLATE.conf apache/httpd.conf
See http://docs.pylonsproject.org/projects/pyramid/1.0/tutorials/modwsgi/index.html for more information about deploying a Pyramid app using mod_wsgi.
WordPress Integration
---------------------
In order to both applications, the main site (Wordpress) and the details site (Python), coexist transparently, we need to add some rules in the webserver.
Basically, the catalog package must be accessible from the Wordpress domain, i.e. *http://books.scielo.org/id/w2* must resolve to *http://admin.books.scielo.org/id/w2*. The latter should not be accessible for users.
Rules to reverse proxy some requests::
# wordpress app virtualhost
<Proxy *>
Allow from all
</Proxy>
ProxyPassMatch ^/staff/(.*)$ http://homolog.backoffice.books.scielo.org/staff/$1
ProxyPassMatch ^/id/(.*)$ http://homolog.backoffice.books.scielo.org/id/$1
ProxyPassMatch ^/static/(.*)$ http://homolog.backoffice.books.scielo.org/static/$1
ProxyPassMatch ^/deform_static/(.*)$ http://homolog.backoffice.books.scielo.org/deform_static/$1
ProxyPassMatch ^/setlang/$ http://homolog.backoffice.books.scielo.org/
ProxyPassMatch ^/login(.*)$ http://homolog.backoffice.books.scielo.org/login$1
ProxyPassMatch ^/logout(.*)$ http://homolog.backoffice.books.scielo.org/logout$1
ProxyPass /admin http://homolog.backoffice.books.scielo.org/login
ProxyPassReverse /admin http://homolog.backoffice.books.scielo.org/login
ProxyPassReverse /staff http://homolog.backoffice.books.scielo.org/staff
Troubleshooting
---------------
The application is updated but seems like the cache is not (even after the apache+mod_wsgi have been restarted)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mod_wsgi has an aggressive cache system. to refresh it, you have to update the date of the .wsgi configuration file and restart apache::
$ touch apache/app/production.wsgi