Differences between revisions 1 and 3 (spanning 2 versions)

Launchpad oops-tools deployment

To deploy a new version of LP's oops-tools instance:

ssh devpad
sudo su - lpqateam
cd /srv/lp-oops.canonical.com/cgi-bin/lpoops
bzr up

If there are changes to the models and/or you need to do data migration (a new migration has been created) then run:

bin/django migrate

Usually there's no need to restart the service after an update. Oops tools has a monitor.py script (see src/oopstools/monitor.py) which monitors changes to .py files and when there are changes to them, it kills the process and starts a new one.

-  ⇤ ← Revision 1 as of 2011-01-10 19:00:17 → 
  Size: 560
  Editor: matsubara
  Comment:
+   ← Revision 3 as of 2011-01-18 15:05:22 → ⇥
  Size: 713
  Editor: matsubara
  Comment: page was renamed from Foundations/QA/OopsToolsDeployment
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+## page was renamed from Foundations/QA/OopsToolsDeployment
-Line 12:
+Line 13:
-If there are changes to the models and/or a new migration has been created then run:
+If there are changes to the models and/or you need to do data migration (a new [[http://south.aeracode.org/docs/whataremigrations.html | migration]] has been created) then run:

launchpad development

Diff for "QA/OopsToolsSetup"

Launchpad oops-tools deployment