Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 131: Line 131:
 
*[http://bitbucket.org/tharris/wormbase-admin WormBase-admin] - ''Administrative code (private)''
 
*[http://bitbucket.org/tharris/wormbase-admin WormBase-admin] - ''Administrative code (private)''
  
== Deprecated Documentation ==
+
= Deprecated Documentation =
  
 
''The good word gone bad. Cruft. Lint. Maybe useful. Probably not.''
 
''The good word gone bad. Cruft. Lint. Maybe useful. Probably not.''
  
==== Rearchitecture ====
+
== Rearchitecture ==
 
*[[HOWTO migrate a CGI|HOWTO migrate a CGI]] - ''quick overview of how to migrate an existing CGI into a Model, Controller, and View. Sparse''
 
*[[HOWTO migrate a CGI|HOWTO migrate a CGI]] - ''quick overview of how to migrate an existing CGI into a Model, Controller, and View. Sparse''
  
Line 146: Line 146:
 
* [[Managing GBrowse]] - ''Quick HowTo for managing GBrowse in development and production environments''
 
* [[Managing GBrowse]] - ''Quick HowTo for managing GBrowse in development and production environments''
  
==== Frozen Releases as Virtual Machines ====
+
== Frozen Releases as Virtual Machines ==
 
* [[How_to_build_a_WormBase_Virtual_Machine|How to build a WormBase Virtual Machine]] -- ''also describes how to create a VMX for a frozen release''
 
* [[How_to_build_a_WormBase_Virtual_Machine|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|Configuring a server to host virtual machines]] -- ''quick guide to setting up a frozen release server''
 
* [[Configuring_a_server_to_host_virtual_machines|Configuring a server to host virtual machines]] -- ''quick guide to setting up a frozen release server''

Revision as of 00:49, 24 December 2010

This page contains information pertinent to employees of WormBase.

Project Management

Web Site Documentation

Development Milestones

July 14 - July 30th

  • Coronate Czars
  • Coding standards and best practices for CSS, Javascript, API in place
  • Release new pages to production powered by the new architecture (classic view only)
    • Variation, Protein, Sequence -- and maybe -- Gene
    • Todd to develop <strikethrough>deployment strategy</strikethrough>, hosting environment, and proxy configuration
    • Abby and Xiaoqi to work up templates and markup specific to the classic view
    • Norie to make requisite API changes as needed

July 30th - August 31st

  • Finish API development of critical classes
  • Finish migration of prominent CGI-based pages to new architecture and release into production (classic view only)
  • Solidify look-and-feel of new site: site map, browsing paths, design patterns, navigation
  • UI features to address/develop
    • Enhanced, high-performance search
    • External URL handling
    • Error trapping and reporting
    • Authorization/Authentication
    • Customizability
    • Configurable two-panel selector
    • Incorporation of old site elements like BLAST/BLAT
    • Top-level species pages (/celegans, eg) and UI clues for distinguishing them

December 22nd, 2010

  • Begin private review of new site
  • Launch surveys on UI

February 1st, 2011

  • Preview new site to SAB

May 1st, 2011

  • Public preview

June 1st, 2011

  • Public launch of new site at International Worm Meeting

Coding standards and Best Practices

Architecture

Software platform

  • Application overview - A quick tour through the software platform, 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
  • Website:Software Platform -- The full software platform, including reverse proxy, webservers, and database node configuration
  • NFS at WormBase

Hardware platform

Administration

Updates

Routine Administration Tasks



Load balancing and Failover

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.

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