| | 1 | = What is a project? = |
| | 2 | |
| | 3 | A BOINC project consists of the following components: |
| | 4 | |
| | 5 | * A [DataBase database] |
| | 6 | * A [ServerDirs directory structure] |
| | 7 | * A [ProjectConfigFile configuration file], which specifies [ProjectOptions options], [ProjectDaemons daemons], and [ProjectTasks periodic tasks]. |
| | 8 | |
| | 9 | Multiple BOINC projects can exist on the same host. This can be handy for creating separate projects for testing and debugging. |
| | 10 | |
| | 11 | The easiest way to create a project is with the [MakeProject make_project] script, which creates skeletal versions of the above components. |
| | 12 | |
| | 13 | A project must be '''stopped''' when maintenance activities (e.g. changing the configuration file or database) are being performed. This is done using [ToolStart project control scripts]. |
| | 14 | |
| | 15 | == The master URL == |
| | 16 | |
| | 17 | Each project is publicly identified by a '''master URL'''. The '''master page''' at this URL has two functions. |
| | 18 | |
| | 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. |
| | 20 | * It contains XML elements of the form |
| | 21 | {{{ |
| | 22 | <scheduler>http://host.domain.edu/cgi/scheduler</scheduler> |
| | 23 | <scheduler>http://host2.domain.edu/cgi/scheduler</scheduler> |
| | 24 | }}} |
| | 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. |
| | 26 | |
| | 27 | '''make_project''' creates a master page in project/html/user/index.php. This file includes the file 'schedulers.txt', which contains the list of <scheduler> elements. |
