pyramid_jinja2 | Jinja2 templating system bindings for the Pyramid web

I am having a really hard time getting my docker container to access the MS SQL server. I have tried following this guide here, but to no avail.

Here is my Base Dockerfile:

Im trying to implement simple authentication in Pyramid by using AuthTktAuthenticationPolicy. I follow this - authentication and this - authorization.

init.py

I'm new to pyramid. When trying to use chameleon as the templating engine, it fails to find the template when specified with a relative path - It is looking for it at env35/lib/python3.5/site-packages/pyramid/ where env35 is the virtual environment I created. It will work however if the full path is specified. It will also work using a relative path using jinja2 as the templating engine. Why can I not use a chameleon template using relative path?

From the manual

add_view(...., renderer,...)

This is either a single string term (e.g. json) or a string implying a path or asset specification (e.g. templates/views.pt) naming a renderer implementation. If the renderer value does not contain a dot ., the specified string will be used to look up a renderer implementation, and that renderer implementation will be used to construct a response from the view return value. If the renderer value contains a dot (.), the specified term will be treated as a path, and the filename extension of the last element in the path will be used to look up the renderer implementation, which will be passed the full path. The renderer implementation will be used to construct a response from the view return value.

Note that if the view itself returns a response (see View Callable Responses), the specified renderer implementation is never called.

When the renderer is a path, although a path is usually just a simple relative pathname (e.g. templates/foo.pt, implying that a template named "foo.pt" is in the "templates" directory relative to the directory of the current package of the Configurator), a path can be absolute, starting with a slash on UNIX or a drive letter prefix on Windows. The path can alternately be a asset specification in the form some.dotted.package_name:relative/path, making it possible to address template assets which live in a separate package.

The renderer attribute is optional. If it is not defined, the "null" renderer is assumed (no rendering is performed and the value is passed back to the upstream Pyramid machinery unmodified).

Here are the steps I undertook to set up my environment...

I have a basic application using Pyramid 1.8 where I want to have a forbidden_view_config to challenge the client.

In my views.py I have: