Difference between revisions of "CSHL documentation"
From WormBaseWiki
Jump to navigationJump to search| Line 45: | Line 45: | ||
* [[Physical structure]] | * [[Physical structure]] | ||
* [[Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting'' | * [[Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting'' | ||
| − | + | ||
* [[Hardware catalog]] | * [[Hardware catalog]] | ||
* [[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'' | ||
| + | |||
| + | ====Load balancing and Failover==== | ||
| + | |||
| + | * [[Building Squid]] - ''How to build and install Squid'' | ||
| + | * [[Configuring Squid]] - ''basic squid configuration at WormBase'' | ||
=== Software platform === | === Software platform === | ||
Revision as of 15:52, 24 September 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.
Contents
Development
- Formal development strategy - An overview of the development process at WormBase
- notes - Best practices, conventions, etc
- Using private development sites - How to use the private, self-contained developer sites on brie3
- libraries - Javascript libraries in use at WormBase
- Using collapsible sections - API for DHTML open/close sections
- Balloon Tooltips - API and architecture for AJAX/DHTML-based tooltips
- Session management - API and architecture for CGI::Session-based state memory and user authentication
- Re-architecture notes/proposals - Notes on new and proposed site-wide architecture changes
Administration
Hardware
General Admin
- Updating WormBase
- General administration
- Monitoring servers
- Emergency plan for server outtages
- Cronjobs
- Managing Perl libraries across nodes
- How to install WormBase from scratch
- Site statistics
- Creating a Google Sitemap
- Optimizing site performance
Virtual Machines / Freezes
- How to build a WormBase Virtual Machine -- also describes how to create a VMX for a frozen release
- Configuring a server to host virtual machines -- quick guide to setting up a frozen release server
- Managing servers hosting virtual machines
- How to build a frozen release -- obsolete; replaced by virtual machines
Reimplementation
Hardware platform
- Logical structure
- Physical structure
- Performance optimization - Memory, Disk, and Network I/O troubleshooting
- Hardware catalog
- 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
Load balancing and Failover
- Building Squid - How to build and install Squid
- Configuring Squid - basic squid configuration at WormBase
Software platform
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
