Developer documentation
From WormBaseWiki
Revision as of 10:13, 16 January 2008 by Tharris (talk | contribs) (New page: This page contains information pertinent to developers of WormBase. = Reimplementation = == Hardware platform == * Logical structure * Physical structure * [[Performance optimiz...)
This page contains information pertinent to developers of WormBase.
Contents
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
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