Django multi-tenancy through Postgres schemas
Project description
django-pgschemas
This package uses Postgres schemas to support data multi-tenancy in a single Django project. It is a fork of django-tenants with some conceptual changes:
- There are static tenants and dynamic tenants. Static tenants can have their own apps and urlconf.
- Tenants can be routed via:
- URL using subdomain or subfolder on shared subdomain
- Session
- Headers
- Public schema should not be used for storing the main site data, but the true shared data across all tenants. Table "overriding" via search path is not encouraged.
- Management commands can be run on multiple schemas via wildcards, either sequentially or in parallel using multithreading.
Documentation
https://django-pgschemas.readthedocs.io/
Contributing
See CONTRIBUTING.md for details on how to contribute to this project.
Credits
- Tom Turner for django-tenants.
- Bernardo Pires for django-tenant-schemas.
- Denish Patel for pg-clone-schema
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file django_pgschemas-1.2.0.tar.gz.
File metadata
- Download URL: django_pgschemas-1.2.0.tar.gz
- Upload date:
- Size: 178.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
8bc456c146032e4348e241ec2d57e4b89862cf4cf8dde36f81da3c0522b6be31
|
|
| MD5 |
500934a367d211e6fb31d2e6e953c840
|
|
| BLAKE2b-256 |
1d7ec11e8f6d944fa855a75adce6eae7f4f37260236364c36cbc5164bac09449
|
Provenance
The following attestation bundles were made for django_pgschemas-1.2.0.tar.gz:
Publisher:
deploy.yaml on lorinkoz/django-pgschemas
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
django_pgschemas-1.2.0.tar.gz -
Subject digest:
8bc456c146032e4348e241ec2d57e4b89862cf4cf8dde36f81da3c0522b6be31 - Sigstore transparency entry: 776220675
- Sigstore integration time:
-
Permalink:
lorinkoz/django-pgschemas@52ec7a1d350d54622ae054283d7f0a4e67522de0 -
Branch / Tag:
refs/heads/master - Owner: https://github.com/lorinkoz
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
deploy.yaml@52ec7a1d350d54622ae054283d7f0a4e67522de0 -
Trigger Event:
workflow_dispatch
-
Statement type:
File details
Details for the file django_pgschemas-1.2.0-py3-none-any.whl.
File metadata
- Download URL: django_pgschemas-1.2.0-py3-none-any.whl
- Upload date:
- Size: 84.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a7cf5ae24a451291c6fdab7974e64ca70ddbfed9554bc444f1b2567669cda906
|
|
| MD5 |
e8a36e11b330edcf827bc5cfad82561e
|
|
| BLAKE2b-256 |
3b74cc8f89317309054f3e9098e170afff7a6ece586b2d9ba286833834b1d171
|
Provenance
The following attestation bundles were made for django_pgschemas-1.2.0-py3-none-any.whl:
Publisher:
deploy.yaml on lorinkoz/django-pgschemas
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
django_pgschemas-1.2.0-py3-none-any.whl -
Subject digest:
a7cf5ae24a451291c6fdab7974e64ca70ddbfed9554bc444f1b2567669cda906 - Sigstore transparency entry: 776220677
- Sigstore integration time:
-
Permalink:
lorinkoz/django-pgschemas@52ec7a1d350d54622ae054283d7f0a4e67522de0 -
Branch / Tag:
refs/heads/master - Owner: https://github.com/lorinkoz
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
deploy.yaml@52ec7a1d350d54622ae054283d7f0a4e67522de0 -
Trigger Event:
workflow_dispatch
-
Statement type: