Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 66: Line 66:
  
 
* [[Website:Testing Overview|Testing Overview]] - ''Overview of our testing strategy''
 
* [[Website:Testing Overview|Testing Overview]] - ''Overview of our testing strategy''
 
  
 
* [[Website:Testing_And_Profiling|Unit Testing and Profiling]] - ''Testing and profiling protocol for the web application''
 
* [[Website:Testing_And_Profiling|Unit Testing and Profiling]] - ''Testing and profiling protocol for the web application''
Line 76: Line 75:
 
* [[Website:Browser Compatibility Statement|Browser Compatibility Testing]] - ''browser support matrix and testing protocol''
 
* [[Website:Browser Compatibility Statement|Browser Compatibility Testing]] - ''browser support matrix and testing protocol''
 
* [[Website:Load Testing|Load Testing]] - ''Performance and load testing; historical benchmarks''
 
* [[Website:Load Testing|Load Testing]] - ''Performance and load testing; historical benchmarks''
 
 
 
 
----
 
----
 
 
 
 
 
*[[Website:Monitoring services|Monitoring services and servers]] - ''Monitoring services and servers''
 
*[[Website:Monitoring services|Monitoring services and servers]] - ''Monitoring services and servers''
  

Revision as of 17:03, 31 July 2011

This page contains information pertinent to employees of WormBase.

Project Management

Data Model and Data Development

Web Site Development Guidelines

Documents pertaining to WormBase 2.0


The Web Application

  • Application overview - An overview of the web application, including MVC structure, request flow, caching, etc
  • Configuration -- Application and view configuration: formatting and standards
  • WormBase::API -- The WormBase data model, maintained external to the web application
  • View -- Templating system, commom template elements, javascript, and CSS
  • Model -- The web application model; thin, glued to the external Model
  • Controller -- Overview of controller files and actions

Information for third party developers

Administration

Architecture

Software Platform

Hardware Platform

Software Life Cycle

Measuring Application Performance


Routine Administration Tasks

Monitoring and Crises Management

Frozen Releases

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

Developer Notes

Deprecated Documentation

The good word gone bad. Cruft. Lint. Maybe useful. Probably not.

Load balancing and Failover

Rearchitecture

  • HOWTO migrate a CGI - quick overview of how to migrate an existing CGI into a Model, Controller, and View. Sparse


Frozen Releases as Virtual Machines