JJ Fliegelman jdotjdot

Nginx TLS SNI routing, based on subdomain pattern

Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.

prerequisites

at least nginx 1.15.9 to use variables in ssl_certificate and ssl_certificate_key.
check nginx -V for the following:
```
...
TLS SNI support enabled
```

	{
	"AWSEBDockerrunVersion": "1",
	"Image": {
	"Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>",
	"Update": "true"
	},
	"Ports": [
	{
	"ContainerPort": "443"
	}

	from django.db import connection, models

	class MyManager(Manager):
	def raw_as_qs(self, raw_query, params=()):
	"""Execute a raw query and return a QuerySet. The first column in the
	result set must be the id field for the model.
	:type raw_query: str \| unicode
	:type params: tuple[T] \| dict[str \| unicode, T]
	:rtype: django.db.models.query.QuerySet
	"""

	class LimitedAdminInlineMixin(object):
	"""
	InlineAdmin mixin limiting the selection of related items according to
	criteria which can depend on the current parent object being edited.

	A typical use case would be selecting a subset of related items from
	other inlines, ie. images, to have some relation to other inlines.

	Use as follows::