15 | | |
16 | | A project must be '''stopped''' when maintenance activities |
17 | | (e.g. changing the configuration file or database) are being performed. |
18 | | This is done using [StartTool project control scripts]. |
19 | | |
20 | | == The master URL == |
21 | | |
22 | | Each project is publicly identified by a '''master URL'''. |
23 | | The '''master page''' at this URL has two functions. |
24 | | |
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. |
27 | | * It contains XML elements of the form |
28 | | {{{ |
29 | | <scheduler>http://host.domain.edu/cgi/scheduler</scheduler> |
30 | | <scheduler>http://host2.domain.edu/cgi/scheduler</scheduler> |
31 | | }}} |
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. |
38 | | |
39 | | Some ISPs remove HTML comments from downloaded pages. |
40 | | To avoid problems with that, an alternative syntax is allowed: |
41 | | {{{ |
42 | | <link rel="boinc_scheduler" href="http://host.domain.edu/cgi/scheduler"> |
43 | | }}} |
44 | | You should still use the `<scheduler>` format too, since older clients won't parse this new syntax. |
45 | | |
46 | | The [MakeProject make_project] script creates a master page in `project/html/user/index.php`. |
47 | | This file includes the file 'schedulers.txt', |
48 | | which contains the list of `<scheduler>` (and `<link>`) elements. |