15 | | * |
| 16 | * Follow the steps below to edit [attachment:skel.conf] for your installation. |
| 17 | |
| 18 | If you put the certificate you created above into {{{fedd.pem}}} all you need to do is change the first line to include the full pathname to your configuration directory. Something like: |
| 19 | |
| 20 | {{{ |
| 21 | base: /my/config/directory |
| 22 | }}} |
| 23 | |
| 24 | If you named the certificate something other than {{{fedd.pem}}}, you need to change the line that starts with {{{cert_file:}}} to point to your file. This means changing the pathname. For example if the certificate was called {{{mycert.pem}}} the line would change to: |
| 25 | |
| 26 | {{{ |
| 27 | cert_file: %(base)s/mycert.pem |
| 28 | }}} |
| 29 | |
| 30 | If the certificate you created has a password, that password must be included as the {{{cert_pwd}}} parameter. For example: |
| 31 | |
| 32 | {{{ |
| 33 | cert_pwd: mypwd |
| 34 | }}} |
| 35 | |
| 36 | In a real installation, including such passwords in the configuration file implies that the configuration file must be secured. |
| 37 | |
| 38 | The next section explains the contents of the configuration files in more detail, but you can skip ahead to running the plug-in if you perfer. |
| 39 | |
| 40 | == Configuration File Contents == |
| 41 | |
| 42 | The [attachment:skel.conf] file contains three sections, each set off by a section name in braces, e.g., {{{[access]}}}. We will explain this file section by section. |
| 43 | |
| 44 | === DEFAULT === |
| 45 | |
| 46 | The first section, {{{[DEFAULT]}}} contains parameters that will be expanded in later sections. The {{{base}}} parameter will be used in other pathnames, to avoid having to hard code each full pathname. In later sections,the {{{%(base)s}}} construction will expand to the contents of the {{{base}}}} parameter. This is a standard construction in a configuration file parsed by python's [http://docs.python.org/library/configparser.html ConfigParser] module. The value inside the {{{%()}}} is the variable to expand, which is followed by a single character for formatting. More information about these conventions is [http://docs.python.org/library/configparser.html available]. |
| 47 | |
| 48 | === access === |