Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 2478:3ab2b91cdd2c
*** empty log message ***
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 17 Jun 2004 08:40:52 +0000 |
| parents | 591e3cfe622a |
| children | 7f9f1c66c1b6 |
comparison
equal
deleted
inserted
replaced
| 2474:591e3cfe622a | 2478:3ab2b91cdd2c |
|---|---|
| 1 ==================== | 1 ==================== |
| 2 Administration Guide | 2 Administration Guide |
| 3 ==================== | 3 ==================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.8 $ | 5 :Version: $Revision: 1.10 $ |
| 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 | 104 |
| 105 python run_tests.py | 105 python run_tests.py |
| 106 | 106 |
| 107 2. If you're using an RDBMS backend, make a backup of its contents now. | 107 2. If you're using an RDBMS backend, make a backup of its contents now. |
| 108 3. Copy your tracker home to a new directory. | 108 3. Make a backup of the tracker home itself. |
| 109 | 109 4. Stop the tracker web and email frontends. |
| 110 Now, working in that copied tracker home: | 110 5. Follow the steps in the `upgrading documentation`_ for the new version of |
| 111 | |
| 112 1. Follow the steps in the `upgrading documentation`_ for the new version of | |
| 113 the software in the copied. | 111 the software in the copied. |
| 114 2. Test each of the admin tool, web interface and mail gateway using the new | 112 6. You may test each of the admin tool, web interface and mail gateway using |
| 115 version of the software. To do this, invoke the scripts directly in the | 113 the new version of the software. To do this, invoke the scripts directly |
| 116 source directory with:: | 114 in the source directory with:: |
| 117 | 115 |
| 118 PYTHONPATH=. python roundup/scripts/roundup_server.py <normal arguments> | 116 PYTHONPATH=. python roundup/scripts/roundup_server.py <normal arguments> |
| 119 PYTHONPATH=. python roundup/scripts/roundup_admin.py <normal arguments> | 117 PYTHONPATH=. python roundup/scripts/roundup_admin.py <normal arguments> |
| 120 PYTHONPATH=. python roundup/scripts/roundup_mailgw.py <normal arguments> | 118 PYTHONPATH=. python roundup/scripts/roundup_mailgw.py <normal arguments> |
| 121 | 119 |
| 122 Once you're comfortable that the upgrade will work using that copy, you | 120 Note that on Windows, this would read:: |
| 123 should upgrade the live version: | 121 |
| 124 | 122 C:\sources\roundup-0.7.4> SET PYTHONPATH=. |
| 125 1. Stop the production web and email frontends. | 123 C:\sources\roundup-0.7.4> python roundup/scripts/roundup_server.py <normal arguments> |
| 126 2. Perform the upgrade steps on the existing tracker directory. | 124 |
| 127 3. Upgrade the software:: | 125 7. Once you're comfortable that the upgrade will work using that copy, you |
| 126 should the installed software:: | |
| 128 | 127 |
| 129 python setup.py install | 128 python setup.py install |
| 130 | 129 |
| 131 4. Restart your tracker. | 130 8. Restart your tracker web and email frontends. |
| 132 | 131 |
| 133 If something bad happens, you may reinstate your backup of the tracker and | 132 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:: | 133 reinstall the older version of the sofware using the same install command:: |
| 135 | 134 |
| 136 python setup.py install | 135 python setup.py install |