Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 42: Line 42:
 
*[[MySQL database replication|MySQL database replication]] - ''Mirroring mysql databases across production nodes''  
 
*[[MySQL database replication|MySQL database replication]] - ''Mirroring mysql databases across production nodes''  
 
*[[Performance optimization|Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting''  
 
*[[Performance optimization|Performance optimization]] - ''Memory, Disk, and Network I/O troubleshooting''  
*[[Hardware catalog|Hardware catalog]] - ''A complete accounting of WormBase compute resources''
+
*[[WormBase_Infrastructure|WormBase Infrastructure]] - ''A complete accounting of WormBase compute resources and topology.
 +
 
 +
 
 
*[[Base node configuration - CentOS5|Base node configuration - CentOS5]] - ''Configuring a WormBase node from scratch (CentOS 5)''
 
*[[Base node configuration - CentOS5|Base node configuration - CentOS5]] - ''Configuring a WormBase node from scratch (CentOS 5)''
 
*[[Building a production node]] - ''Configuring a new production node''
 
*[[Building a production node]] - ''Configuring a new production node''

Revision as of 10:52, 4 May 2010

This page contains information pertinent to employees of WormBase.

Project Management

Web Site Documentation

Rearchitecture Design Stages

  1. Requirements analysis / Design Specifications
  2. Architecture Outline
  3. Prototyping
  4. Formal Development via established conventions
    1. Formal development strategy - An overview of the development process at WormBase
    2. Developer notes - Best practices, conventions, etc
    3. Coding standards
  5. Testing
  6. Deployment

Software platform

Hardware platform


--

Administration

Routine Administration Tasks

Load balancing and Failover

Monitoring and Crises Management

Frozen Releases

Frozen Releases as Virtual Machines

Updates

Developer Tools

All Hands Meeting Agendas and Notes

Source Code Repositories

We use the distributed source code management system Mercurial. Projects are hosted on BitBucket.

How-To create, check out, and manage our repositories

Deprecated Documentation

The good word gone bad. Cruft. Lint. Maybe useful but probably not.