Skip to content
Django multi-tenancy using PostgreSQL schemas
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
django_pgschemas
docs
dpgs_sandbox
.coveragerc
.editorconfig
.gitignore
.readthedocs.yml
.travis.yml
LICENSE
README.rst
pyproject.toml

README.rst

django-pgschemas

Packaging: poetry Code style: black Join the chat at https://gitter.im/django-pgschemas Build status Documentation status Code coverage PyPi version

This app uses PostgreSQL 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 are routed both via subdomain and via subfolder on shared subdomain.
  • Public is no longer the schema for storing the main site data. Public should be used only for true shared data across all tenants. Table "overriding" via search path is no longer encouraged.
  • Management commands can be run on multiple schemas via wildcards - the multiproc behavior of migrations was extended to just any tenant command.

Documentation

https://django-pgschemas.readthedocs.io/

Contributing

Credits

  • Tom Turner for django-tenants
  • Bernardo Pires for django-tenant-schemas
  • Vlada Macek for django-schemata
You can’t perform that action at this time.