Changes between Version 1 and Version 2 of InstallVSO


Ignore:
Timestamp:
07/30/12 14:41:57 (12 years ago)
Author:
joe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • InstallVSO

    v1 v2  
    1111}}} 
    1212 
    13 Modify the file as appropriate so it'll install where you want, and knows about the super-secret place where the VSO perl scripts are.  I'd also recommend that you look over what the script's doing, as it's generally a bad idea to just download stuff from the internet and run it.  (also, it's going to download a [http://sdac.virtualsolar.org/Installers/ConfigAll.PL Perl script] part way through and run it to set up all of the local configuration bits) 
     13or  
    1414 
    15 == The Manual Bits == 
     15{{{ 
     16curl -O http://sdac.virtualsolar.org/Installers/install_vso.sh 
     17}}} 
    1618 
     19If you don't have `curl` or `wget` installed ... that's a problem, as you'll need something to fetch the dependancies and such. 
    1720 
    18 For everyone: 
     21Modify the file as appropriate so it'll install where you want, and knows about the super-secret place where the VSO perl scripts are.  I'd also recommend that you look over what the script's doing, as it's generally a bad idea to just download stuff from the internet and run it.  (also, it's going to download other scripts part way through and run it under `sudo` to set up all of the local configuration bits ... set `PAUSE_AFTER_DOWNLOAD` to get it to wait for you to inspect 'em first) 
    1922 
    20 1. Make it so the webserver can see the static HTML files. 
     23== install the CGIs and static files == 
    2124 
    22   (I'm assuming you have it being told that the static files are it something like `http://server/vso`, and they're locally in `/opt/vso/html`, and the webserver root is `/var/www/html`) 
     25Once the scripts have finished running, you should get a message similar to: 
    2326 
    24   Depending on your webserver's security, you might be able to just symlink it in: 
     27{{{ 
     28To finish the install: 
    2529 
    26  {{{ 
     30   copy files in /tmp/cgi to the local path for http://servername.example.com/cgi-bin/vso 
     31   
     32   copy files in /opt/vso/html to the local path for http://servername.example.com/vso 
     33}}} 
     34 
     35We'll assume for this example that the webserver root is `/var/www/html` and the CGI root is `/var/www/cgi-bin` 
     36 
     37You have a few options for the static files: 
     38 
     39  1. Symlink the directories 
     40 
     41{{{ 
    2742   ln -s /opt/vso/html /var/www/html/vso  
    2843}}} 
    2944 
    30   But if you don't allow symlinks, you can define an alias in either `httpd.conf` or the appropriate `site/*.conf` file for that virtual host: 
     45  The only advantage is that you won't have to do anything in the future after updates.  Many web servers don't allow symlinks (and it's a good idea not to), so you may get reports in your webserver's error log such as: 
     46 
     47{{{ 
     48Symbolic link not allowed or link target not accessible: /var/www/html/vso 
     49}}} 
     50 
     51 
     52  2. Set up an `Alias` in the `httpd.conf` file or the appropriate `site/*.conf` file for that virtual host: 
    3153 
    3254{{{ 
    … …  
    3456}}} 
    3557 
    36   But that might not work if you followed the CIS benchmarks to the letter (not allowing access to files outside of the web root), so in that case, just copy 'em in place: 
     58  You will need to restart your webserver ( issue the command `apachectl graceful` ).  
     59 
     60  This might not work if you followed the CIS benchmarks to the letter (not allowing access to files outside of the web root) 
     61 
     62  3. Or, just copy the files into place: 
    3763 
    3864{{{ 
    … …  
    4066}}} 
    4167 
    42 2. Put all of the CGIs in place 
    4368 
    44   First, you're going to have to decide which set of CGIs you're going to use, as there's multiple versions of most of 'em. 
    4569 
    46   Like before, you can either symlink into `/var/www/cgi-bin/vso` add a `ScriptAlias` directive  (Alias + designate as CGI) to the webserver config, or just copy 'em in place 
     70.. 
    4771 
    48   If you're using Fast CGI (and you've already installed the FCGI perl module, if not, run `cpanm FCGI`), you will need the following files: 
     72for the CGIs, you really want to copy them into place.  Barring any errors, they'll have been copied into `/tmp/cgi` with the appropriate names to use. 
    4973 
    5074{{{ 
    51         cartfi.cgi       -> carti 
    52         cartufi.pl       -> cartui 
    53         searchFormufi.pl -> search 
    54         show_details.pl  -> show_details 
    55         vsoufi.cgi       -> vsoui 
    56         vsofi.cgi        -> vsoi 
    57  
    58         (optional bits) 
    59         catalogufi.pl     -> catalog 
    60         vsofi_wsdl.cgi    -> vsoi_wsdl 
    61         vsoi_tabdelim.cgi -> vsoi_tabdelim 
     75cp -r /tmp/cgi /var/www/cgi-bin/vso 
    6276}}} 
    6377 
    64  If you're using mod_perl ... contact me, as it looks like they're not all packed in. 
     78(note to self -- they don't check to see if you over rode the filenames when configuring; they assume the default names)  
    6579 
    66  If you're using basic CGI: 
    6780 
    68 {{{ 
    69         carti.cgi       -> carti 
    70         cartui.pl       -> cartui 
    71         searchForm.pl   -> search 
    72         show_details.pl -> show_details 
    73         vsoui.cgi       -> vsoui 
    74         vsoi.cgi        -> vsoi 
    7581 
    76         (optional bits) 
    77         catalog.pl        -> catalog 
    78         vsoi_wsdl.cgi     -> vsoi_wsdl 
    79         vsoi_tabdelim.cgi -> vsoi_tabdelim 
    80 }}} 
     82== Modify the Web UI configuration (if appropriate) == 
    8183 
    82  It's very likely that the files won't parse clean, because we've put the perl libraries in a strange place. So, you'll need to pop them open, and add the following line (adjusted to your system): 
    83  
    84 {{{ 
    85 use lib '/opt/vso/lib/perl5'; 
    86 }}} 
    87  
    88  You can then check the files using the command: 
    89  
    90 {{{ 
    91 perl -wc filename 
    92 }}} 
    93  
    94  If you get a `Can't locate` message, check to make sure that the `@INC contains:` bit includes what you have listed in the `use lib` line.  If it's still got problems, [People/JoeHourcle  e-mail me]. 
    95  
    96 3. Modify the `webui_config.xml` file so it knows about itself: 
    97   (note to self -- automate this part, as it should all come from the config, and we need to trim out the old bits) 
     84This is only necessary if you're running the 'UI' (web front end) portions of the VSO.  If you're only running the APIs, this isn't necessary. 
    9885 
    9986 edit : `/opt/vso/etc/webui_config.xml`