| | 1 | = BOINC project (UC Berkeley) tasks = |
| | 2 | |
| | 3 | == Web site == |
| | 4 | |
| | 5 | The BOINC web site (https://boinc.berkeley.edu) is currently hosted |
| | 6 | on isaac.ssl.berkeley.edu, which runs Scientific Linux. |
| | 7 | |
| | 8 | Post news items as needed. |
| | 9 | |
| | 10 | Isaac runs a number of software systems: |
| | 11 | |
| | 12 | * Trac |
| | 13 | * Mediawiki |
| | 14 | * MySQL |
| | 15 | * Apache |
| | 16 | * PHP |
| | 17 | |
| | 18 | These may need to be upgraded periodically. |
| | 19 | |
| | 20 | TODO: document our configuration for these systems. |
| | 21 | |
| | 22 | TODO: a plan for migrating the server to a different machine or VM if isaac dies. |
| | 23 | |
| | 24 | TODO: move as much from BOINC server to github as possible. |
| | 25 | E.g. the trac wiki and mediawiki pages. |
| | 26 | Rom looked at this; there are some conversion tools but they didn't work completely. |
| | 27 | |
| | 28 | == Code-signing key == |
| | 29 | |
| | 30 | Maintain the code-signing key used for Win. We get this from Comodo, and it's about $100/year. |
| | 31 | |
| | 32 | |
| | 33 | == Project list maintenance == |
| | 34 | |
| | 35 | [AdminApprovedProjects Maintain list of approved projects and account managers] |
| | 36 | (approve a project after you talk to its admins and are convinced that |
| | 37 | it description is accurate and they know about server security and are doing code-signing). |
