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