Difference between revisions of "CSHL documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 48: Line 48:
 
* [[Physical structure]]
 
* [[Physical structure]]
 
* [[Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting''
 
* [[Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting''
 
 
* [[Hardware catalog]] - ''A complete accounting of WormBase compute resources''
 
* [[Hardware catalog]] - ''A complete accounting of WormBase compute resources''
 
* [[Base node configuration - CentOS5]] - ''Configuring a WormBase node from scratch (CentOS 5)''
 
* [[Base node configuration - CentOS5]] - ''Configuring a WormBase node from scratch (CentOS 5)''
 
 
* [[Crises Recovery Plan]] - ''Everything breaks at some point. Here's how to fix it''
 
* [[Crises Recovery Plan]] - ''Everything breaks at some point. Here's how to fix it''
  

Revision as of 15:14, 3 October 2007

The WormBase Cold Spring Harbor team is in charge of developing, maintaining, and hosting WormBase. This page contains links to documentation relating to those topics.

Development

Administration

Hardware

General Admin

Virtual Machines / Freezes

Developer Tools


Reimplementation

Hardware platform

Software platform

Administration

Load balancing and Failover

Logging, Monitoring, and Reporting

Development notes by release

As part of the formal development strategy at WormBase, software freezes occur on the Wednesday before the release of each new database. This corresponds with the CSHL WormBase conference call.

For a new feature to enter production, developers must send an email to cshl@wormbase.org by the software freeze deadline briefly describing the new feature and any new module or database requirements. This section collates those notes for easy access