Changes between Version 46 and Version 47 of Archive/SeattleGeniInstallation

Changes between Version 46 and Version 47 of Archive/SeattleGeniInstallation

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 46 and Version 47 of Archive/SeattleGeniInstallation

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 46 and Version 47 of Archive/SeattleGeniInstallation

Show
Ignore:
Timestamp:
07/14/12 14:52:47 (7 years ago)
Author:
leonwlaw
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archive/SeattleGeniInstallation

    v46 v47  
    1 = SeattleClearinghouse Installation !HowTo = 
    2  
    3 This document explains how to do a fresh install of the SeattleClearinghouse portal on 
     1= Seattle Clearinghouse Installation !HowTo = 
     2 
     3This document explains how to do a fresh install of the Seattle Clearinghouse portal on 
    44a machine that is running a Debian-like Linux operating system such as Ubuntu. 
    55 
    6  * For info on deploying the production SeattleClearinghouse code and for starting/restarting Apache, see [wiki:SeattleGeniProductionHttp] 
     6 * For info on deploying the production Seattle Clearinghouse code and for starting/restarting Apache, see [wiki:SeattleGeniProductionHttp] 
    77 
    88---- 
     
    1212---- 
    1313 
    14 SeattleClearinghouse requires at least the following software to be installed: 
     14Seattle Clearinghouse requires at least the following software to be installed: 
    1515  
    16  * [http://www.python.org/ Python] -- the language SeattleClearinghouse is written in 
     16 * [http://www.python.org/ Python] -- the language Seattle Clearinghouse is written in 
    1717 * [http://mysql-python.sourceforge.net/ Python MySQLDB] -- the python mysql interface 
    1818 * [http://www.mysql.com/ MySQL] -- the database 
     
    6363 
    6464[[BR]] 
    65 == Deploying and running SeattleClearinghouse == 
     65== Deploying and running Seattle Clearinghouse == 
    6666---- 
    6767 
     
    229229---- 
    230230 
    231 To provide encryption, SeattleClearinghouse relies on SSL. Therefore you will need to 
     231To provide encryption, Seattle Clearinghouse relies on SSL. Therefore you will need to 
    232232setup two !VirtualHost entries at the minimum: one for connections to 
    233233port 80 (HTTP), and one for connections to port 443 (SSL). 
     
    299299}}} 
    300300 
    301 To use this configuration for your SeattleClearinghouse installation, change "mysite" to your domain 
     301To use this configuration for your Seattle Clearinghouse installation, change "mysite" to your domain 
    302302name, change "/home/geni/live/" in the site media location and Python path to the directory 
    303 where you deployed SeattleClearinghouse, and make sure "/admin_media" is aliased to a valid directory, 
     303where you deployed Seattle Clearinghouse, and make sure "/admin_media" is aliased to a valid directory, 
    304304as the exact location will vary depending on the version of Python installed and how you 
    305305installed Django. A good place to put this configuration is the file /etc/apache2/sites-enabled/000-default. 
     
    329329}}} 
    330330 
    331 For importing all the required modules, Apache requires read and execute permissions for the seattle and seattlegeni directories. To ensure Apache has the correct permissions, run the following command in your SeattleClearinghouse directory: 
     331For importing all the required modules, Apache requires read and execute permissions for the seattle and seattlegeni directories. To ensure Apache has the correct permissions, run the following command in your Seattle Clearinghouse directory: 
    332332{{{ 
    333333#!sh 
     
    335335}}} 
    336336 
    337 If you try to access your SeattleClearinghouse installation's website now, then it's possible you'll see an exception like this: 
     337If you try to access your Seattle Clearinghouse installation's website now, then it's possible you'll see an exception like this: 
    338338{{{ 
    339339Cannot open file for translation '/home/geni/live/seattle/rsa.repy': [Errno 13] Permission denied: '/home/geni/live/seattle/rsa_repy.py' 
     
    352352---- 
    353353 
    354 If you have all the components of SeattleClearinghouse (including Apache) configured, 
     354If you have all the components of Seattle Clearinghouse (including Apache) configured, 
    355355the script deploymentscripts/start_seattlegeni_components.sh will start up all the individual 
    356356components in the correct order. 
     
    360360username, and create the directory for LOG_DIR if it doesn't already exist. 
    361361 
    362 First, if one or more of the SeattleClearinghouse scripts is already running, kill them before running start_seattlegeni_components.sh. 
     362First, if one or more of the Seattle Clearinghouse scripts is already running, kill them before running start_seattlegeni_components.sh. 
    363363 
    364364To run start_seattlegeni_components.sh, run the following commands with the correct directory substituted for /home/geni/live: 
     
    384384---- 
    385385 
    386 Congratulations! You should now have a fully operational SeattleClearinghouse 
     386Congratulations! You should now have a fully operational Seattle Clearinghouse 
    387387installation that you can access at https://mysite/geni/