Difference between revisions of "CSHL documentation"
From WormBaseWiki
Jump to navigationJump to search| Line 54: | Line 54: | ||
*[[Coding standards]] | *[[Coding standards]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
== Administration == | == Administration == | ||
* [[Monitoring services and servers]] | * [[Monitoring services and servers]] | ||
| − | |||
* [[Crises Recovery Plan]] - ''Everything breaks. Here's how to fix it.'' | * [[Crises Recovery Plan]] - ''Everything breaks. Here's how to fix it.'' | ||
===Load balancing and Failover=== | ===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 == | ||
Revision as of 15:26, 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.
Contents
Development
- Formal development strategy - An overview of the development process at WormBase
- Developer notes - Best practices, conventions, etc
- Using private development sites - How to use the private, self-contained developer sites on brie3
- Javascript 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
Administration
Hardware
General Admin
- Updating WormBase
- General administration
- Monitoring servers
- Emergency plan for server outtages
- Cronjobs
- Managing Perl libraries across nodes
- 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 -- how to configure a WormBase VM as a frozen release server
- Creating Virtual Disks - How to create VMDKs for unlimited portable storage
Developer Tools
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
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
