Mercurial > p > roundup > code
changeset 7504:1a912887d704
Clarify meaning of 'tracker directory' in upgrading doc.
now shown as 'tracker home directory' and link to 'tracker home' in
glossary added. Also expand on how to identify the tracker home in the
glossary term.
Prompted by question on irc at: 2023-06-21 09:38:37
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 21 Jun 2023 14:43:31 -0400 |
| parents | 7b6278da3faa |
| children | 62409b4a3a52 |
| files | doc/glossary.txt doc/upgrading-history.txt |
| diffstat | 2 files changed, 4 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/glossary.txt Wed Jun 21 14:34:37 2023 -0400 +++ b/doc/glossary.txt Wed Jun 21 14:43:31 2023 -0400 @@ -60,7 +60,8 @@ the schema and hyperdb that forms one issue tracker tracker home - the physical location on disk of a tracker + the physical location on disk of a tracker. It has the + ``config.ini``, ``schema.py`` files for the tracker. -----------------
--- a/doc/upgrading-history.txt Wed Jun 21 14:34:37 2023 -0400 +++ b/doc/upgrading-history.txt Wed Jun 21 14:43:31 2023 -0400 @@ -182,8 +182,8 @@ method, therefore the default search permissions will not allow searching and you'll have to add an explicit search permission. If you have modified your schema, you can check if you're missing any -search permissions with the following script, run it in your tracker -directory, it will list for each Class and Property the roles that may +search permissions with the following script, run it in your :term:`tracker +home` directory, it will list for each Class and Property the roles that may search for this property:: #!/usr/bin/python