=====
bab CMS
=====
Light CMS Django app.
Quick start
-----------
1. Add "bab_cms" to your INSTALLED_APPS setting like this::
INSTALLED_APPS = [
...
'bab_cms',
]
2. Include the cms URLconf in your project urls.py like this::
path('cms/', include('bab_cms.urls')),
3. Run `python manage.py migrate` to create the cms models.
4. Start the development server and visit http://127.0.0.1:8000/admin/
to create posts and articles (you'll need the Admin app enabled).
5. Visit http://127.0.0.1:8000/cms/ to participate in the CMS.
bab CMS
=====
Light CMS Django app.
Quick start
-----------
1. Add "bab_cms" to your INSTALLED_APPS setting like this::
INSTALLED_APPS = [
...
'bab_cms',
]
2. Include the cms URLconf in your project urls.py like this::
path('cms/', include('bab_cms.urls')),
3. Run `python manage.py migrate` to create the cms models.
4. Start the development server and visit http://127.0.0.1:8000/admin/
to create posts and articles (you'll need the Admin app enabled).
5. Visit http://127.0.0.1:8000/cms/ to participate in the CMS.
Metadata
Release files for django-bab-project 0.1
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 | |
|---|---|---|---|---|
| django-bab-project-0.1.tar.gz | 3.9 kB | Without provenance | Details |
Release files / django-bab-project-0.1.tar.gz
| Download URL | django-bab-project-0.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcbd9f9376b268d330d8d393f0f58a8af83dffdec7ce2c02ac2222aece4c5bb0
|
|
BLAKE2b-256 checksum How to use checksums |
50cf9f0f13cbbfba9981bff90b90bb70eff1e47897e62f58594989f97795c25e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for django-bab-project 0.1
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.