Hi Bern:

In message <1559572570.81.0.0716488299242.issue2551029@roundup.psfhosted.org>,
Bernhard Reiter writes:
>Okay, I can get something rendered when changing to
>
>template_engine = jinja2
>
>so the initialisation progess did not set the right template_engine.

Hmm, ok how to handle this? There is no way for install to know what
template engine should be used.

Should that be another NO DEFAULT setting? If so how is the user to
know which of the three settings (or possibly some hybrid) to use?

Maybe we neeed a config.ini.deploy that gets installed into the
tracker working directory, loaded and then deleted. The
config.ini.deploy would include only:

   template_engine = jinja2

or any other template specific settings.

Then the normal save operation for config.ini will generate an
properly updated config.ini?

Thoughts?

>Also missing are the static files needed, there is no css and no javascript:
>127.0.0.1 - - [03/Jun/2019 14:33:59] "GET /support/ HTTP/1.1" 200 -
>127.0.0.1 - - [03/Jun/2019 14:33:59] code 404, message
>/support/@@file/style.css
>127.0.0.1 - - [03/Jun/2019 14:33:59] "GET /support/@@file/style.css
>HTTP/1.1" 404 -
>127.0.0.1 - - [03/Jun/2019 14:33:59] code 404, message
>/support/@@file/bootstrap.min.css
>127.0.0.1 - - [03/Jun/2019 14:33:59] "GET
>/support/@@file/bootstrap.min.css HTTP/1.1" 404 -

Are there special directions for deploying the jinja2 template?  IIRC
bootstrap is under 3rdparty. Maybe that directory needs to be copied
into html as an extra step?

>127.0.0.1 - - [03/Jun/2019 14:33:59] code 404, message
>/support/@@file/bootstrap-responsive.min.css

Note there is a ticket that Christof is working for updating this
template to boostrap 4. Boostrap 4 doesn't have a separate responsive
css file. It's all in the base.