This Django app routes requests for specific hosts to different URL schemes defined in modules called “hostconfs”.
For example, if you own example.com but want to serve specific content at api.example.com and beta.example.com, add the following to a hosts.py file:
from django_hosts import patterns, host
host_patterns = patterns('path.to',
host(r'api', 'api.urls', name='api'),
host(r'beta', 'beta.urls', name='beta'),
)
This causes requests to {api,beta}.example.com to be routed to their corresponding URLconf. You can use your urls.py as a template for these hostconfs.
Patterns are evaluated in order. If no pattern matches, the request is processed in the usual way, ie. using the standard ROOT_URLCONF.
The patterns on the left-hand side are regular expressions. For example, the following ROOT_HOSTCONF setting will route foo.example.com and bar.example.com to the same URLconf.
from django_hosts import patterns, host
host_patterns = patterns('',
host(r'(foo|bar)', 'path.to.urls', name='foo-or-bar'),
)
Installation
First, install the app with your favorite package manager, e.g.:
pip install django-hosts
Alternatively, use the repository on Github.
You can find the full docs here: django-hosts.rtfd.org
Then configure your Django site to use the app:
Add 'django_hosts' to your INSTALLED_APPS setting.
Add 'django_hosts.middleware.HostsMiddleware' to your MIDDLEWARE_CLASSES setting.
Create a module containing your default host patterns, e.g. in the hosts.py file next to your urls.py.
Set the ROOT_HOSTCONF setting to the dotted Python import path of the module containing your host patterns, e.g.:
ROOT_HOSTCONF = 'mysite.hosts'
Set the DEFAULT_HOST setting to the name of the host pattern you want to refer to as the default pattern. It’ll be used if no other pattern matches or you don’t give a name to the host_url template tag.
1 maintainer
Metadata
1 maintainer
Release files for django-hosts 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-hosts-0.5.tar.gz | 26.1 kB | Without provenance | Details for django-hosts-0.5.tar.gz |
Release files / django-hosts-0.5.tar.gz
| Download URL | django-hosts-0.5.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce8ce8a1c8563d1f12ef6e8d1511802c18137062222991664b98d97cac21adf8
|
|
BLAKE2b-256 checksum How to use checksums |
26dce48d44a341e891a0954094e2188e265af5d2582be3a5079748a30c3917e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-hosts 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
