2002-07-29 19:01:38 +00:00
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
|
|
|
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
|
|
|
|
|
<html lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<title>Operational Tools: Applications and Versions</title>
|
|
|
|
|
<meta name="generator" content="BBEdit 6.1.2">
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<h2>Operational Tools: Applications and Versions</h2>
|
2002-05-24 04:29:10 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
BOINC provides a few tools for creating and operating projects:
|
|
|
|
|
</p>
|
2002-05-24 04:29:10 +00:00
|
|
|
<ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
<li>
|
|
|
|
|
Utility programs (such as <b>add</b> and <b>create_work</b>).
|
|
|
|
|
These can be run manually or invoked from scripts.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
C++ functions (such as <b>create_work()</b>).
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
Web interfaces (currently these provide only read access).
|
|
|
|
|
</li>
|
2002-05-24 04:29:10 +00:00
|
|
|
</ul>
|
2002-07-29 19:01:38 +00:00
|
|
|
Projects can create their own tools, either at a low level (e.g.
|
|
|
|
|
directly accessing the BOINC DB from PHP or Perl scripts) or by using
|
|
|
|
|
the BOINC DB C++ API (db/db.h). <h3>The Add utility program</h3>
|
2002-05-24 04:29:10 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The program <b>add</b> performs various types of initialization:
|
|
|
|
|
</p>
|
2002-05-24 04:29:10 +00:00
|
|
|
<dl>
|
2002-07-29 19:01:38 +00:00
|
|
|
<dt>
|
|
|
|
|
add app -app_name name
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Create a new application (just creates a DB record).
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
add platform name -platform_name name
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Create a platform record (just creates a DB record);
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
add app_version
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
-app_name x
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
-platform_name y
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
-version a
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
-download_dir d
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
-url_base e
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
-exec_dir b
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
[ -message x ]
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
[ -message_priority y ]
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
[ -code_sign_keyfile x -exec_files file1 file2 ... ]
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
[ -signed_exec_files file1 sign1 file2 sign2 ... ]
|
|
|
|
|
</dd>
|
|
|
|
|
<dd>
|
|
|
|
|
<br>
|
|
|
|
|
Create an app_version record. Copy the executable file(s) from
|
|
|
|
|
the compilation directory (-exec_dir) to the download directory. If
|
|
|
|
|
-exec_files is used, each executable file is signed using the given
|
|
|
|
|
private key; this should be used only for test/debug purposes. If
|
|
|
|
|
-signed_exec_files is used, the signatures are passed explicitly; this
|
|
|
|
|
should be used for production purposes, where the signatures are
|
|
|
|
|
generated on an offline computer. If -message is used, the version is
|
|
|
|
|
tagged with the given message and optional priority.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
add user -email_addr x -name y -web_password z -authenticator a
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Create a user record.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
add prefs -email_addr x -prefs_file y
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Create a preference set, and make it the default preferences for
|
|
|
|
|
the given user.
|
|
|
|
|
</dd>
|
2002-05-24 04:29:10 +00:00
|
|
|
</dl>
|
2002-07-29 19:01:38 +00:00
|
|
|
<h3>Web Interfaces</h3>
|
2002-05-24 04:29:10 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The file <b>show_db.php</b> in the operational web site directory
|
|
|
|
|
displays the contents of the BOINC DB.
|
|
|
|
|
</p>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
