Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 2475:debf57fc8c0f maint-0.7
more doc
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 17 Jun 2004 05:49:22 +0000 |
| parents | 3f66eb446aa4 |
| children | d22796ad33f6 |
comparison
equal
deleted
inserted
replaced
| 2457:3fe516581aa3 | 2475:debf57fc8c0f |
|---|---|
| 1 ==================== | 1 ==================== |
| 2 Administration Guide | 2 Administration Guide |
| 3 ==================== | 3 ==================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.5.2.1 $ | 5 :Version: $Revision: 1.5.2.2 $ |
| 6 | 6 |
| 7 .. contents:: | 7 .. contents:: |
| 8 | 8 |
| 9 What does Roundup install? | 9 What does Roundup install? |
| 10 ========================== | 10 ========================== |
| 98 ---------------- | 98 ---------------- |
| 99 | 99 |
| 100 Always make a backup of your tracker before upgrading software. Steps you may | 100 Always make a backup of your tracker before upgrading software. Steps you may |
| 101 take: | 101 take: |
| 102 | 102 |
| 103 1. ensure that the unit tests run on your system | 103 1. Ensure that the unit tests run on your system: |
| 104 2. copy your tracker home to a new directory | 104 |
| 105 3. follow the steps in the upgrading documentation for the new version of | 105 python run_tests.py |
| 106 the software | 106 |
| 107 4. test each of the admin tool, web interface and mail gateway using the new | 107 2. If you're using an RDBMS backend, make a backup of its contents now. |
| 108 version of the software | 108 3. Copy your tracker home to a new directory. |
| 109 5. stop the production web and email frontends | 109 |
| 110 6. perform the upgrade steps on the existing tracker directory | 110 Now, working in that copied tracker home: |
| 111 7. upgrade the software | 111 |
| 112 8. restart your tracker | 112 1. Follow the steps in the `upgrading documentation`_ for the new version of |
| 113 the software in the copied. | |
| 114 2. Test each of the admin tool, web interface and mail gateway using the new | |
| 115 version of the software. To do this, invoke the scripts directly in the | |
| 116 source directory with:: | |
| 117 | |
| 118 PYTHONPATH=. python roundup/scripts/roundup_server.py <normal arguments> | |
| 119 PYTHONPATH=. python roundup/scripts/roundup_admin.py <normal arguments> | |
| 120 PYTHONPATH=. python roundup/scripts/roundup_mailgw.py <normal arguments> | |
| 121 | |
| 122 Once you're comfortable that the upgrade will work using that copy, you | |
| 123 should upgrade the live version: | |
| 124 | |
| 125 1. Stop the production web and email frontends. | |
| 126 2. Perform the upgrade steps on the existing tracker directory. | |
| 127 3. Upgrade the software:: | |
| 128 | |
| 129 python setup.py install | |
| 130 | |
| 131 4. Restart your tracker. | |
| 132 | |
| 133 If something bad happens, you may reinstate your backup of the tracker and | |
| 134 reinstall the older version of the sofware using the same install command:: | |
| 135 | |
| 136 python setup.py install | |
| 113 | 137 |
| 114 | 138 |
| 115 Migrating Backends | 139 Migrating Backends |
| 116 ------------------ | 140 ------------------ |
| 117 | 141 |
| 202 | 226 |
| 203 Back to `Table of Contents`_ | 227 Back to `Table of Contents`_ |
| 204 | 228 |
| 205 .. _`Table of Contents`: index.html | 229 .. _`Table of Contents`: index.html |
| 206 .. _`customisation documentation`: customizing.html | 230 .. _`customisation documentation`: customizing.html |
| 207 | 231 .. _`upgrading documentation`: upgrading.html |
| 232 |