MyyearbookDeploy » History » Revision 2
Revision 1 (Aurynn Shaw, 01/02/2007 01:12 PM) → Revision 2/3 (Aurynn Shaw, 01/02/2007 01:12 PM)
= Deployment Instructions = PG Server: 216.139.233.201 == System Changes == * Added a crontab entry under the Admin account to collect statistics. * Running the forward.py script, hosted in the directory /var/www/pggraph/myyearbook/ * Forwarded port is 7735 == pggraph local settings == * Prefix used is myyearbook * uses the cmd authentication credentials * Cronjob is == Preparing http://www.cmdalert.com == * symlink all the scripts into the containing directory, with a copy of the config.ini * Verify the existence of the pggraph2 database, and all the functions and types have been created. * Configure the INI file: * Local database, pggraph_radioparadise * SSH connection to radioparadise, likely using the cmd administrative account? * Authentication on their postgres server. postgres user, or cmd user? * Determine their pricing plan for pggraph statistics, and set shortest interval accordingly * Decide on a prefix - radio_paradise * Run the installer. Prayer would not be averse at this point. * Start up forward.py. It will read the connection info from the config file and initiate a tunnel to www.radioparadise.com * Edit bridge.py, to use the absolute path to your config file. * run bridge.py, verify that it actually works. * Add a cronjob for bridge.py, set to every 10 minutes. 5 minutes, or so. == Apache == * Decide on where radioparadise will be able to view their statistics * Configure apache to expose the directory where pggraph2 is installed to the web, as a CGI directory. * Allow .py to execute via python * Mark pggraph_index.py, pggraph_database.py, and pggraph_table.py as +x * Test them. Again, prayer is not unadvisable.