Changes between Version 4 and Version 5 of MovingTrac

Timestamp:

07/16/2012 05:38:19 AM (10 months ago)

Author:

exarkun

Comment:

summaries

MovingTrac

@@ -13 +13 @@
 An SVN post-commit hook also pushes SVN changes to trac along a second channel using a PB server deployed with trac.  The post-commit hook needs the correct address for that PB server, which will need to move along with the trac server.
 
-trac and kenaan (an IRC commit/notification bot) also interact.  trac uses programs from lp:twisted-trac-integration to send messages to kenaan.  For this, trac needs to be configured with the correct address at which kenaan is listening.  If kenaan is not moved at the same time as trac, the configuration probably needs to change from pointing at localhost to pointing across a network.  If kenaan is moved, other things pointing at it need to be updated.
+trac and kenaan (an IRC commit/notification bot) also interact.  trac uses programs from lp:twisted-trac-integration to send messages to kenaan.  For this, trac needs to be configured with the correct address at which kenaan is listening.  If kenaan is not moved at the same time as trac, the configuration probably needs to change from pointing at localhost to pointing across a network.  If kenaan is moved, other things pointing at it need to be updated.  The location of kenaan is configured inside lp:twisted-trac-integration.
 
 Once the database moves, the high scores daemon needs to be moved as well, since it talks to the same database.
@@ -28 +28 @@
   - postgres
   - highscores server
+  - svn mirror
+  - svn post-commit config update
+  - private trac pb server for accepting commit notification
+  - lp:twisted-trac-integration, with updated configuration to point at kenaan
+
+And the list of things that need to be updated but not ''necessarily'' re-deployed onto the new host with trac:
+
   - diffresource
-  - svn mirror
 
 Other questions: