Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 64: Line 64:
  
 
== Profiling ==
 
== Profiling ==
* [[Testing|Testing and Profiling]] - ''Testing and profiling guidelines for the web application''
+
* [[Website:Testing_And_Profiling|Testing and Profiling]] - ''Testing and profiling guidelines for the web application''
 
* [[Website:Profiling|Profiling]] - ''Profiling the web application, performance tuning, and historical benchmarks''
 
* [[Website:Profiling|Profiling]] - ''Profiling the web application, performance tuning, and historical benchmarks''
 
* [[Website:Profiling|Profiling]] - ''Profiling the web application, performance tuning, and historical benchmarks''
 
* [[Website:Profiling|Profiling]] - ''Profiling the web application, performance tuning, and historical benchmarks''

Revision as of 15:08, 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

Profiling

  • Testing and Profiling - Testing and profiling guidelines for the web application
  • Profiling - Profiling the web application, performance tuning, and historical benchmarks
  • Profiling - Profiling the web application, performance tuning, and historical benchmarks
  • Monitoring - Monitoring services: local and remote

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