An Open Source content management system build to compliment the [Mezzanine CMS](https://github.com/stephenmcd/mezzanine), by adding the concept of Modular Pages and block admin for multi-model change lists.
## Installation
+ Install django-clubhouse with `pip install django-clubhouse`
+ Add `mezzanine.conf`, `mezzanine.core`, `mezzanine.generic`, `mezzanine.pages`, `mezzanine.twitter` to `INSTALLED_APPS` in your Django settings module
+ Add `clubhouse.core`, `clubhouse.contrib`, `clubhouse.forms` to `INSTALLED_APPS` in your Django Settings module
+ Add the following snippet to the end of the Django settings module:
```python
try:
from clubhouse.utils.conf import set_dynamic_settings
except ImportError:
pass
else:
set_dynamic_settings(globals())
```
Metadata
Release files for django-clubhouse 0.2.22
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-clubhouse-0.2.22.tar.gz | 341.4 kB | Without provenance | Details for django-clubhouse-0.2.22.tar.gz |
Release files / django-clubhouse-0.2.22.tar.gz
| Download URL | django-clubhouse-0.2.22.tar.gz |
|---|---|
| Size | 341.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23d7fbee48deda670c50aa71f2a87f50166129922ecd46a7d100fb850977cba0
|
|
BLAKE2b-256 checksum How to use checksums |
2fba464586cffb7330f6c71dae9f12d83216d75ebf350c623919b9fdcc93017d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-clubhouse 0.2.22
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.