Pakistan Deployment Cycle

• UAT: ​http://test.eden.sahanafoundation.org
• Live: ​http://pakistan.sahanafoundation.org

We want to do daily upgrades of the system:

1. Upgrade Live with code release from UAT

• Send a notification to the list (for testers) with a summary of the day's changes: Full list of fixed bugs to be verified, New features to be Tested

2. Upgrade UAT to Trunk code

• Send a notification to the list (for users) with a summary of yesterday's code changes: Focussed on new features & notable bug fixes

3. Refresh the UAT database with data from Live

Notifications can be built with info from:

• LP ChangeLog: ​https://code.launchpad.net/~flavour/sahana-eden/trunk
• Trac Timeline: http://eden.sahanafoundation.org/timeline

• UserGuidelinesUpgrade

Sysadmin ToDo

• Confirm versions of all base software the same on both sides
• Set deployment_settings on UAT to the same as Prod
• Configure Apache Maintenance site

  ln -sf /etc/apache2/sites-available/maintenance ln -sf
  /etc/apache2/sites-enabled/pakistan
  
  This should be enhanced by:
   * keeping access to phpMyAdmin
   * allowing access to site through a browser - but using a different
  name (which we don't publish)
   * improving the text on the maintenance page
  

• Extend scripts:
  • ConfigurationGuidelines#Usefulaliases

    pull
    migrate (CLI web2py load as 'su web2py')
    migrateoff
    DBsync (tbc)
    

Later

• Investigate a fix or alternative to ​http://trac-hacks.org/wiki/MathCaptchaPlugin for allowing Trac users to register bugs anonymously whilst not locking out our testing team.
• Schedule the Ushahidi imports
  • Can we pass URL as argument?

---

Pakistan