Changes between Version 5 and Version 6 of ServerComponents


Ignore:
Timestamp:
Dec 10, 2012, 4:27:23 PM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ServerComponents

    v5 v6  
    55 * A [DataBase database]
    66 * A [ServerDirs directory structure]
    7  * A [ProjectConfigFile configuration file], which specifies [ProjectOptions options], [ProjectDaemons daemons], and [ProjectTasks periodic tasks].
     7 * A [ProjectConfigFile configuration file], which specifies [ProjectOptions options],
     8   [ProjectDaemons daemons], and [ProjectTasks periodic tasks].
    89
    9 Multiple BOINC projects can exist on the same host. This can be handy for creating separate projects for testing and debugging.
     10Multiple BOINC projects can exist on the same host.
     11This can be handy for creating separate projects for testing and debugging.
    1012
    11 The easiest way to create a project is with the [MakeProject make_project] script, which creates all the above components.
     13The easiest way to create a project is with the [MakeProject make_project] script,
     14which creates all the above components.
    1215
    13 A project must be '''stopped''' when maintenance activities (e.g. changing the configuration file or database) are being performed. This is done using [StartTool project control scripts].
     16A project must be '''stopped''' when maintenance activities
     17(e.g. changing the configuration file or database) are being performed.
     18This is done using [StartTool project control scripts].
    1419
    1520== The master URL ==
    1621
    17 Each project is publicly identified by a '''master URL'''. The '''master page''' at this URL has two functions.
     22Each project is publicly identified by a '''master URL'''.
     23The '''master page''' at this URL has two functions.
    1824
    19  * It is the home page of the project; when viewed in a browser it describes the project and contains links for registering and for downloading the core client.
     25 * It is the home page of the project; when viewed in a browser it describes the project
     26   and contains links for registering and for downloading the BOINC client.
    2027 * It contains XML elements of the form
    2128{{{
    … …  
    2330<scheduler>http://host2.domain.edu/cgi/scheduler</scheduler>
    2431}}}
    25  that give the URLs of the project's scheduling servers. These tags can be embedded within HTML comments. The BOINC core client reads and parses the master page to locate scheduling servers. If at any point it is unable to connect to any scheduling server for a project, it rereads the master page. This mechanism lets a project move or add scheduling servers.
     32 that give the URLs of the project's scheduling servers.
     33 These tags can be embedded within HTML comments.
     34 The BOINC client reads and parses the master page to locate scheduling servers.
     35 If at any point it is unable to connect to any scheduling server for a project,
     36 it rereads the master page.
     37 This mechanism lets a project move or add scheduling servers.
    2638
    27 Some ISPs remove HTML comments from downloaded pages. To avoid problems with that, an alternative syntax is allowed:
     39Some ISPs remove HTML comments from downloaded pages.
     40To avoid problems with that, an alternative syntax is allowed:
    2841{{{
    2942<link rel="boinc_scheduler" href="http://host.domain.edu/cgi/scheduler">
    … …  
    3144You should still use the `<scheduler>` format too, since older clients won't parse this new syntax.
    3245
    33 The [MakeProject make_project] script creates a master page in `project/html/user/index.php`. This file includes the file 'schedulers.txt', which contains the list of `<scheduler>` (and `<link>`) elements.
     46The [MakeProject make_project] script creates a master page in `project/html/user/index.php`.
     47This file includes the file 'schedulers.txt',
     48which contains the list of `<scheduler>` (and `<link>`) elements.