|
2 | 2 | Maintaining Roundup Trackers |
3 | 3 | ============================ |
4 | 4 |
|
5 | | -:Version: $Revision: 1.1 $ |
| 5 | +:Version: $Revision: 1.2 $ |
6 | 6 |
|
7 | 7 | .. contents:: |
8 | 8 | :depth: 1 |
@@ -59,6 +59,30 @@ Migrating Backends |
59 | 59 | 9. restart web and email frontends |
60 | 60 |
|
61 | 61 |
|
| 62 | +Moving a Tracker |
| 63 | +================ |
| 64 | + |
| 65 | +If you're moving the tracker to a similar machine, you should: |
| 66 | + |
| 67 | +1. install Roundup on the new machine and test that it works there, |
| 68 | +2. stop the existing tracker web and email frontends (preventing changes), |
| 69 | +3. copy the tracker home directory over to the new machine, and |
| 70 | +4. start the tracker web and email frontends on the new machine. |
| 71 | + |
| 72 | +Most of the backends are actually portable across platforms (ie. from Unix to |
| 73 | +Windows to Mac). If this isn't the case (ie. the tracker doesn't work when |
| 74 | +moved using the above steps) then you'll need to: |
| 75 | + |
| 76 | +1. install Roundup on the new machine and test that it works there, |
| 77 | +2. stop the existing tracker web and email frontends (preventing changes), |
| 78 | +3. use the roundup-admin tool "export" command to export the contents of |
| 79 | + the existing tracker, |
| 80 | +4. copy the export to the new machine, |
| 81 | +5. use the roundup-admin "import" command to import the tracker on the new |
| 82 | + machine, and |
| 83 | +6. start the tracker web and email frontends on the new machine. |
| 84 | + |
| 85 | + |
62 | 86 | ------------------- |
63 | 87 |
|
64 | 88 | Back to `Table of Contents`_ |
|
0 commit comments