Difference between revisions of "CSHL documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 57: Line 57:
  
  
= Reimplementation =
 
 
== Hardware platform ==
 
 
* [[Logical structure]]
 
* [[Physical structure]]
 
* [[Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting''
 
* [[Hardware catalog]] - ''A complete accounting of WormBase compute resources''
 
* [[Base node configuration - CentOS5]] - ''Configuring a WormBase node from scratch (CentOS 5)''
 
 
== Software platform ==
 
 
*[[Installing the Web Application]] - ''Here's how to install the WormBase web application -- including Catalyst -- on your system''
 
*[[Development Process]] - ''An overview of the development process''
 
*[[Coding standards]]
 
*[[Third-party libraries]] - ''installing and managing third-party libraries, namely GBrowse and BioPerl''
 
 
== Administration ==
 
 
* [[Monitoring services and servers]]
 
* [[Crises Recovery Plan]] - ''Everything breaks. Here's how to fix it.''
 
 
===Load balancing and Failover===
 
* [[Building Squid]] - ''How to build and install Squid''
 
* [[Configuring Squid]] - ''basic squid configuration at WormBase''
 
  
 
== Development notes by release ==
 
== Development notes by release ==
Line 101: Line 76:
 
* [[WS158]]
 
* [[WS158]]
 
* [[WS157]]
 
* [[WS157]]
 
= [[Developer_meetings|Developer Meetings]] =
 
 
[[2008.01-Toronto| 14-17 January 2008 - Toronto]]
 

Revision as of 10:21, 16 January 2008

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.

Much of this documentation will be obsolete shortly. Please see Developer documentation for up-to-date documents.

Development

Administration

Hardware

General Admin

Virtual Machines / Freezes

Developer Tools


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