===
**gu-django-multihost** is a Django application/framework which allow to serve different hostnames "
"and urlconfs in one django application instance
Quickstart:
===
Install gu-django-multihost:
$ pip install gu-django-multihost
Add gu-multihost to INSTALLED_APPS in settings.py for your project:
INSTALLED_APPS = (
...
'gu_multihost',
)
#multihost
MULTIHOST_DATABASE_DRIVEN_URLS = True # means that list or url modules are stored in database and managed there
#for MULTIHOST_DATABASE_DRIVEN_URLS = False make a list possilbe selections for sites urls
from gu_multihost import MULTIHOST_DEFAULT_URLS
MULTIHOST_AVAILABLE_URLS = MULTIHOST_DEFAULT_URLS + [ROOT_URLCONF, ]
Add middleware class fetch from cache middleware :
MIDDLEWARE_CLASSES += (
# should be called after FetchFromCacheMiddleware
'gu_multihost.middleware.MultiHostMiddleware',
'django.middleware.cache.FetchFromCacheMiddleware',
)
Setup you'r multihost sites objects.
Standard core django sites host names should be configured to actual accesible domain names with protocol name and port values without ending slash:
https://site-name.org:8433
In your code:
import gu_multihost
Yu can query current site, which serves a request:
gu_multihost.get_current_site.site # link to django site object
You can build urls for different sites with a full url.
gu_multihost.mh_reverse(news_item, site=None, full_url=False, [site.two_letter_code, nid])
Build short url for default site - /BB/news/item/XXX/
gu_multihost.mh_reverse(news_item, site=None, full_url=False, [site.two_letter_code, nid])
Build full url for default site - http://default.site/BB/news/item/XXX/
gu_multihost.mh_reverse(news_item, site=mobile, full_url=False, [site.two_letter_code, nid])
Build full url for separate site - http://mobile.site/BB/ni/XXX/
The same is from django templates:
{% import multihost %}
{% mh_reverse 'portal-news-item' '' 'pb' %}
{% mh_reverse 'portal-news-item' 'mobile' 'pb' %}
License (and related information):
===
Originally written by Andriy Gushuley.
This program is licensed under the MIT License (see LICENSE.txt)
Metadata
Release files for gu-django-multihost 1.2.0
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 |
|---|---|---|---|---|
| gu-django-multihost-1.2.0.tar.gz | 5.7 kB | Without provenance | Details for gu-django-multihost-1.2.0.tar.gz |
Release files / gu-django-multihost-1.2.0.tar.gz
| Download URL | gu-django-multihost-1.2.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
582e7d5d158d1cb0ac62d23641858648ab6b6b71d40b50f4bd29b92b0b2cad2a
|
|
BLAKE2b-256 checksum How to use checksums |
76e1a74c2954b4f563d081e30ae25c66d626a6caa09d80289e8808e1cc36c47d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gu-django-multihost 1.2.0
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.