A BOINC project involves of the following components:

The easiest way to set up a basic server is to use the make_project script, which creates skeletal versions of the above components.

A project is described by a configuration file. A basic configuration file is generated by make_project. Some changes to a project require editing the configuration file.

A project must be stopped when maintenance activities (e.g. changing the configuration file or database) are being performed. This is accomplish using project control scripts.

The scripts can be used to create multiple BOINC projects on the same host. This can be handy for creating separate projects for testing and debugging.

The master URL

Each project is publicly identified by a master URL. The master page at this URL has two functions.

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.
It contains XML elements of the form
```
";
echo htmlspecialchars("
http://host.domain.edu/cgi/scheduler
http://host2.domain.edu/cgi/scheduler
");
echo"
```
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 change the locations of its scheduling servers, or add new servers.

make_project creates a master page in project/html/user/index.php. This file includes the file 'schedulers.txt', which contains the list of ", htmlspecialchars(""), "elements. "; page_tail(); ?>