vigiboard / apache / README.txt @ 7b54a690
History | View | Annotate | Download (1.58 KB)
1 |
#Here is a numbered list of what you need to do to deploy you Turbogears2 or Pylons application. Follow 1 through 6. |
---|---|
2 |
|
3 |
#1. Create production.ini configuration file if its not there already. Example: |
4 |
cp development.ini production.ini |
5 |
#Edit production.ini and delete the port settings or make sure its set to 80. |
6 |
|
7 |
#2. Change or check the apache settings file. |
8 |
#Edit /usr/local/turbogears/vigiboard/apache/vigiboard and make sure it has the necessary apache configurations you need. |
9 |
#Copy {vigiboard} apache config file to apache folder. Example: |
10 |
cp /usr/local/turbogears/vigiboard/apache/vigiboard /etc/apache2/sites-available/vigiboard |
11 |
|
12 |
#3.Check if permissions are the same as other apache sites usually (root:root) |
13 |
|
14 |
ls -l /etc/apache2/sites-available/ |
15 |
#You shoud see |
16 |
#total 16 |
17 |
#-rw-r--r-- 1 root root 950 2008-08-08 13:06 default |
18 |
#-rw-r--r-- 1 root root 7366 2008-08-08 13:06 default-ssl |
19 |
#-rw-r--r-- 1 root root 1077 2008-11-08 12:38 vigiboard |
20 |
|
21 |
#4.Enable your site. |
22 |
a2ensite vigiboard |
23 |
|
24 |
#5. Check if your project has proper permissions, usually apache user. (Example: www-data:www-data on Debian). |
25 |
ls -l /usr/local/turbogears/vigiboard/apache/ |
26 |
#total 16 |
27 |
#-rw-r--r-- 1 www-data www-data 1077 2008-11-26 22:35 vigiboard |
28 |
#-rw-r--r-- 1 www-data www-data 2319 2008-11-26 23:25 vigiboard.wsgi |
29 |
#-rw-r--r-- 1 www-data www-data 594 2008-11-26 22:35 README.txt |
30 |
#-rw-r--r-- 1 www-data www-data 538 2008-11-26 22:35 test.wsgi |
31 |
|
32 |
#6.Reload apache |
33 |
/etc/init.d/apache2 reload |
34 |
|
35 |
|
36 |
#You are done. Your application should be working. Check the access.log, warn.log, and error.log in /var/log/apache to see if there are any errors. |