Changes between Version 13 and Version 14 of ToolUpgrade


Ignore:
Timestamp:
Jan 23, 2008, 2:40:23 PM (16 years ago)
Author:
Eric Myers
Comment:

INSTALL_DIR environment variable is not checked; use --project_dir

Legend:

Unmodified
Added
Removed
Modified

  • ToolUpgrade

    v13 v14  
    11= Upgrading server software =
    22
    3 The BOINC server software (scheduler, daemons, web pages) is continually improved and debugged. We recommend that projects upgrade to the latest version every few weeks or so. There may also be points upgrades are mandatory to continue working with current client software.
     3The BOINC server software (scheduler, daemons, web pages) is continually improved and debugged. We recommend that projects upgrade to the latest version every few weeks or so. There may also be points where upgrades are mandatory to continue working with current client software.
    44We maintain a list of [ServerUpdates recent changes].
    55
    6 The steps in upgrading are as follows:
     6The steps required to upgrade are as follows:
    77
    88 1. (Optional) Stop the project, and make backups of the project database and the project tree.
    … …  
    1313$ ./upgrade project_name
    1414}}}
    15   The upgrade script copies files from the `source/html/`, `source/sched` and `source/tool` directories to the corresponding project directories (the default project root directory is `$HOME/projects/project_name`; upgrade takes an optional environment variables `INSTALL_DIR` specifying the project's root directory).
     15  The upgrade script copies files from the `source/html/`, `source/sched` and `source/tool` directories to the corresponding project directories.
    1616
    17  To copy only the web pages (PHP files) use
     17 The default project root directory is `$HOME/projects/project_name`.  If this is not where your project lives then you also need to use the `--project_root` flag to specify the location of the directory above where your project lives, like so:
     18{{{
     19$ ./upgrade --project_root /path/to/projects  project_name
     20}}}
     21 The project directory would then be `/path/to/projects/project_name`.  This allows for several BOINC projects to co-exist on the same server.
     22
     23 It is possible to update only the web pages (PHP files), using the `--web_only` flag:
    1824{{{
    1925$ ./upgrade --web_only  project_name
    … …  
    2127 (There is no option to update only the server software but not the web pages, but there should be.)
    2228
    23  4. Update your project's database if needed:
     29 4. Update your project's database, if needed.   First
    2430{{{
    2531$ cd project/html/ops
    2632}}}
    27  and look at the file `db_update.php`. This has a number of functions with names like
     33 and look at the file `db_update.php`.  This has a number of functions in it with names like
    2834{{{
    29 #!php
    3035update_8_05_2005()
    3136}}}
    32   Each function performs a particular database update. You must perform all updates, in sequence, since your last server software upgrade. (If you're not sure when that was, you can use `mysql` to see that current format of your database, e.g., to see the fields in the `user` table, type
     37  Each function performs a particular database update. You must perform all updates, in sequence, starting from  your last server software upgrade. If you are not sure when that was, you can use `mysql` to see that current format of your database.  For example, to see the fields in the `user` table, type
    3338{{{
    3439$ mysql project_name
    … …  
    4045}}}
    4146 Repeat this for the necessary updates, in increasing chronological order.
     47 1. Check file permissions and ownership of the feeder, scheduler, etc.
    4248 1. Start the project, and check log files to make sure everything is OK. Run the BOINC client and test basic functions (attaching to project, getting work).