Mercurial > p > roundup > code
comparison doc/customizing.txt @ 5367:f3b844fda420
Updated links to handle:
http://issues.roundup-tracker.org/issue2550965
I think I have most of them at this point.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 18 Jul 2018 21:32:24 -0400 |
| parents | 979390afb001 |
| children | b7fa56ced601 d698d3d843a9 |
comparison
equal
deleted
inserted
replaced
| 5366:b87a1f51ac32 | 5367:f3b844fda420 |
|---|---|
| 64 schema`_. Some configuration is also performed using permissions - see the | 64 schema`_. Some configuration is also performed using permissions - see the |
| 65 `security / access controls`_ section. For example, to allow users to | 65 `security / access controls`_ section. For example, to allow users to |
| 66 automatically register through the email interface, you must grant the | 66 automatically register through the email interface, you must grant the |
| 67 "Anonymous" Role the "Email Access" Permission. | 67 "Anonymous" Role the "Email Access" Permission. |
| 68 | 68 |
| 69 The following is taken from the `Python Library Reference`__ (May 20, 2004) | 69 The following is taken from the `Python Library Reference`__ (July 18, 2018) |
| 70 section "ConfigParser -- Configuration file parser": | 70 section "ConfigParser -- Configuration file parser": |
| 71 | 71 |
| 72 The configuration file consists of sections, led by a "[section]" header | 72 The configuration file consists of sections, led by a [section] header |
| 73 and followed by "name = value" entries, with line continuations on a | 73 and followed by name: value entries, with continuations in the style |
| 74 newline with leading whitespace. Note that leading whitespace is removed | 74 of RFC 822 (see section 3.1.1, “LONG HEADER FIELDS”); name=value is |
| 75 from values. The optional values can contain format strings which | 75 also accepted. Note that leading whitespace is removed from |
| 76 refer to other values in the same section. Lines beginning with "#" or ";" | 76 values. The optional values can contain format strings which refer to |
| 77 are ignored and may be used to provide comments. | 77 other values in the same section, or values in a special DEFAULT |
| 78 section. Additional defaults can be provided on initialization and | |
| 79 retrieval. Lines beginning with '#' or ';' are ignored and may be | |
| 80 used to provide comments. | |
| 78 | 81 |
| 79 For example:: | 82 For example:: |
| 80 | 83 |
| 81 [My Section] | 84 [My Section] |
| 82 foodir = %(dir)s/whatever | 85 foodir = %(dir)s/whatever |
| 83 dir = frob | 86 dir = frob |
| 84 | 87 |
| 85 would resolve the "%(dir)s" to the value of "dir" ("frob" in this case) | 88 would resolve the "%(dir)s" to the value of "dir" ("frob" in this case) |
| 86 resulting in "foodir" being "frob/whatever". | 89 resulting in "foodir" being "frob/whatever". |
| 87 | 90 |
| 88 __ http://docs.python.org/lib/module-ConfigParser.html | 91 __ https://docs.python.org/2/library/configparser.html |
| 89 | 92 |
| 90 Example configuration settings are below. | 93 Example configuration settings are below. |
| 91 | 94 |
| 92 Section **main** | 95 Section **main** |
| 93 database -- ``db`` | 96 database -- ``db`` |
| 2692 reverse only on Multilink properties - produce a list of the linked | 2695 reverse only on Multilink properties - produce a list of the linked |
| 2693 items in reverse order | 2696 items in reverse order |
| 2694 isset returns True if the property has been set to a value | 2697 isset returns True if the property has been set to a value |
| 2695 =========== ================================================================ | 2698 =========== ================================================================ |
| 2696 | 2699 |
| 2697 __ http://docs.python.org/lib/module-time.html | 2700 __ https://docs.python.org/2/library/time.html |
| 2698 | 2701 |
| 2699 All of the above functions perform checks for permissions required to | 2702 All of the above functions perform checks for permissions required to |
| 2700 display or edit the data they are manipulating. The simplest case is | 2703 display or edit the data they are manipulating. The simplest case is |
| 2701 editing an issue title. Including the expression:: | 2704 editing an issue title. Including the expression:: |
| 2702 | 2705 |
| 4323 | 4326 |
| 4324 Using an LDAP database for user information | 4327 Using an LDAP database for user information |
| 4325 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 4328 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 4326 | 4329 |
| 4327 A script that reads users from an LDAP store using | 4330 A script that reads users from an LDAP store using |
| 4328 http://python-ldap.sf.net/ and then compares the list to the users in the | 4331 https://pypi.org/project/python-ldap/ and then compares the list to the users in the |
| 4329 roundup user database would be pretty easy to write. You'd then have it run | 4332 roundup user database would be pretty easy to write. You'd then have it run |
| 4330 once an hour / day (or on demand if you can work that into your LDAP store | 4333 once an hour / day (or on demand if you can work that into your LDAP store |
| 4331 workflow). See the example `Using a UN*X passwd file as the user database`_ | 4334 workflow). See the example `Using a UN*X passwd file as the user database`_ |
| 4332 for more information about doing this. | 4335 for more information about doing this. |
| 4333 | 4336 |