RadioParadiseDeploy » History » Version 4
Aurynn Shaw, 12/27/2006 12:17 PM
1 | 1 | Aurynn Shaw | |
---|---|---|---|
2 | 4 | Aurynn Shaw | h1. Deployment Instructions |
3 | |||
4 | |||
5 | 1 | Aurynn Shaw | www.radioparadise.com |
6 | |||
7 | |||
8 | 4 | Aurynn Shaw | h2. Preparing http://www.cmdalert.com |
9 | 1 | Aurynn Shaw | |
10 | |||
11 | 4 | Aurynn Shaw | * symlink all the scripts into the containing directory, with a copy of the config.ini |
12 | * Verify the existence of the pggraph2 database, and all the functions and types have been created. |
||
13 | * Configure the INI file: |
||
14 | *** Local database, pggraph_radioparadise |
||
15 | *** SSH connection to radioparadise, likely using the cmd administrative account? |
||
16 | *** Authentication on their postgres server. postgres user, or cmd user? |
||
17 | *** Determine their pricing plan for pggraph statistics, and set shortest interval accordingly |
||
18 | *** Decide on a prefix - radio_paradise |
||
19 | * Run the installer. Prayer would not be averse at this point. |
||
20 | * Start up forward.py. It will read the connection info from the config file and initiate a tunnel to www.radioparadise.com |
||
21 | * Edit bridge.py, to use the absolute path to your config file. |
||
22 | * run bridge.py, verify that it actually works. |
||
23 | * Add a cronjob for bridge.py, set to every 5 minutes, or so. |
||
24 | |||
25 | |||
26 | h2. Apache |
||
27 | |||
28 | |||
29 | * Decide on where radioparadise will be able to view their statistics |
||
30 | * Configure apache to expose the directory where pggraph2 is installed to the web, as a CGI directory. |
||
31 | * Allow .py to execute via python |
||
32 | * Mark pggraph_index.py, pggraph_database.py, and pggraph_table.py as +x |
||
33 | * Test them. Again, prayer is not unadvisable. |