view doc/tracker_templates.txt @ 6503:4c7381f5051b

Enable bionic build replacing xenail Enable bionic 18.04 replacing xenial 16.04. Curl https://oligarchy.co.uk/xapian/ is failing to validate the SSL cert with the CA on xenial. See if this fixes it. Python 3.4 is not supported on bionic is obsolete so remove testing. It was retained because 3.4 was EPEL version for centos 7. With centos demise, removed it from 'python:' settings. Test latest 2.x release, earliest 3.x release supported by bionic (3.6), last two production 3.x releases and nightly to cut down on cost of testing. Also run tests in 3.x series in reverse order so 3.9 runs first. Hence we fail early as newest pythons seem to have more issues with the code.
author John Rouillard <rouilj@ieee.org>
date Thu, 30 Sep 2021 20:31:29 -0400
parents b76be13e027e
children 3f3ce3004013
line wrap: on
line source

=========================
Roundup Tracker Templates
=========================

The templates distributed with Roundup are stored in the "share" directory
nominated by Python. On Unix this is typically
``/usr/share/roundup/templates/`` (or ``/usr/local/share...``) and
on Windows this is ``c:\python22\share\roundup\templates\``.

The template loading looks in four places to find the templates:

1. *share* - eg. ``<prefix>/share/roundup/templates/*``.
   This should be the standard place to find them when Roundup is
   installed.
2. ``<roundup.admin.__file__>/../templates/*``.
   This will be used if Roundup's run in the distro (aka. source)
   directory.
3. ``<current working dir>/*``.
   This is for when someone unpacks a 3rd-party template.
4. ``<current working dir>``.
   This is for someone who "cd"s to the 3rd-party template dir.

Templates contain:

- modules ``schema.py`` and ``initial_data.py``
- directories ``html``, ``detectors`` and ``extensions``
  (with appropriate contents)
- optional ``config_ini.ini`` file. It is structured like a tracker's
  ``config.ini`` but contains only headers (e.g. ``[main]``) and
  *required* parameters that are different from defaults:
  e.g. ``template_engine = jinja2`` and ``static_files =
  static``. These settings override the default values saved to the
  tracker's ``config.ini``.
- template "marker" file ``TEMPLATE-INFO.txt``, which contains
  the name of the template, a description of the template
  and its intended audience.

An example TEMPLATE-INFO.txt::

 Name: classic
 Description: This is a generic issue tracker that may be used to track bugs,
              feature requests, project issues or any number of other types
              of issues. Most users of Roundup will find that this template
              suits them, with perhaps a few customisations.
 Intended-For: All first-time Roundup users


Roundup Issue Tracker: http://roundup-tracker.org/