Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 6163:c2fd254c9257
Doc updates/indexing.
doc/admin_guide.txt, doc/customizing.txt, doc/features.txt,
doc/installation.txt, doc/mysql.txt, doc/postgresql.txt: adding
index entries
doc/customizing.txt: reference schema changes later in document in
addition to wiki.
website/www/contents.txt: make wiki url https:.... Remove
indices/tables as they don't show up in web interface. Put
docs/announcement.txt into hidden toctree to silence warning from
sphinx. Announcement.txt is referenced from index.txt so can't
silence by adding to conf.py exclude_patern.
website/www/index.txt: mention security and other improvements in jinja2
templates.
website/www/conf.py: get rid of all warning by using exclude_patterns
to ignore docs that aren't included. Remove exclude_trees using
exclude_pattern instead. Make html_add_permalinks value acceptable
so no warning reported.
website/www/_static/style.css, website/www/_templtes/layout.html:
add prev/next/index links for all doc pages.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 13 May 2020 00:40:14 -0400 |
| parents | 4f74b97dddcd |
| children | 82f58ae89142 |
comparison
equal
deleted
inserted
replaced
| 6162:9cfdbfc6d8ed | 6163:c2fd254c9257 |
|---|---|
| 287 reinstall the older version of the sofware using the same install command:: | 287 reinstall the older version of the sofware using the same install command:: |
| 288 | 288 |
| 289 python setup.py install | 289 python setup.py install |
| 290 | 290 |
| 291 | 291 |
| 292 .. index:: database; convert from one database backend to another | |
| 293 | |
| 292 Migrating Backends | 294 Migrating Backends |
| 293 ------------------ | 295 ------------------ |
| 294 | 296 |
| 295 1. Stop the existing tracker web and email frontends (preventing changes). | 297 1. Stop the existing tracker web and email frontends (preventing changes). |
| 296 2. Use the roundup-admin tool "export" command to export the contents of | 298 2. Use the roundup-admin tool "export" command to export the contents of |
| 336 4. copy the export to the new machine, | 338 4. copy the export to the new machine, |
| 337 5. use the roundup-admin "import" command to import the tracker on the new | 339 5. use the roundup-admin "import" command to import the tracker on the new |
| 338 machine, and | 340 machine, and |
| 339 6. start the tracker web and email frontends on the new machine. | 341 6. start the tracker web and email frontends on the new machine. |
| 340 | 342 |
| 343 .. index:: | |
| 344 pair: roundup; migrate from other bugtracker software | |
| 341 | 345 |
| 342 Migrating From Other Software | 346 Migrating From Other Software |
| 343 ----------------------------- | 347 ----------------------------- |
| 344 | 348 |
| 345 You have a couple of choices. You can either use a CSV import into Roundup, | 349 You have a couple of choices. You can either use a CSV import into Roundup, |
| 362 | 366 |
| 363 where ``<designator>`` is the item's ``<classname><id>`` combination. | 367 where ``<designator>`` is the item's ``<classname><id>`` combination. |
| 364 The ``<N>`` value is ``int(<id> / 1000)``. | 368 The ``<N>`` value is ``int(<id> / 1000)``. |
| 365 | 369 |
| 366 | 370 |
| 371 .. index:: pair: roundup-admin; managing users | |
| 372 | |
| 367 Adding A User From The Command-Line | 373 Adding A User From The Command-Line |
| 368 ----------------------------------- | 374 ----------------------------------- |
| 369 | 375 |
| 370 The ``roundup-admin`` program can create any data you wish to in the | 376 The ``roundup-admin`` program can create any data you wish to in the |
| 371 database. To create a new user, use:: | 377 database. To create a new user, use:: |