Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 6: Line 6:
 
*[[Project meeting agendas and minutes]]
 
*[[Project meeting agendas and minutes]]
 
*[[Linking To WormBase|Linking To WormBase]]  
 
*[[Linking To WormBase|Linking To WormBase]]  
 +
 +
*[[SOPs|Internal documentation and standard operating procedures]]
 +
*[[Orthologs: use cases for searches]]
 +
 +
= Data Model and Data Development =
 +
 +
*[[WormBase Models]]
 +
*[[Genome Standards]] -- ''What criteria should a genome meet before we accept it for integration?''
 
*[[Suggested pre-release data checks|Suggested pre-release data checks]]  
 
*[[Suggested pre-release data checks|Suggested pre-release data checks]]  
*[[SOPs|Internal documentation and standard operating procedures]]
 
 
*[[modENCODE Analysis & metadata discussion|modENCODE Analysis & metadata discussion]]
 
*[[modENCODE Analysis & metadata discussion|modENCODE Analysis & metadata discussion]]
*[[Genome Standards]] -- ''What criteria should a genome meet before we accept it for integration?''
 
*[[WormBase Models]]
 
*[[Orthologs: use cases for searches]]
 
 
*[[Genome sequence changes]]
 
*[[Genome sequence changes]]
 
*[[WormBase Genomes]]
 
*[[WormBase Genomes]]

Revision as of 19:01, 5 January 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

Administration

Architecture

Software Platform

Hardware Platform

Updates

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

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