Django CMS QE
Django CMS Quick & Easy provides all important modules to run new page without a lot of coding. Aims to do it very easily and securely.
For more information please read documentation or GitLab.
Development
To prepare your dev environment run this command:
make prepare-dev (run with apt get update)
make prepare-env
Caution! It is allowed only Python >= 3.9 due to typing:
VENV_PYTHON=/usr/bin/python3.9 make prepare-venv
To prepare the explicit python version into the explicit folder:
VENV_PATH=/home/username/venv VENV_PYTHON=/usr/bin/python3.9 make prepare-venv
export VENV_PATH=/home/username/venv
To run tests or lint use this commands:
make test
make lint
To run only particular test:
make test=cms_qe_table/tests/test_utils.py::test_get_model_by_table test
To run example use this command:
make run-example
To call other Django commands:
make cmd (List django commands, same like --help)
make cmd=dbshell cmd
make cmd='createsuperuser --username=dave --email=dave@rd.foo' cmd
To find more useful commands, run just make.
Upgrade
To upgrade from version 2.2 to version >= 3.0.0, you can use the DjangoCMS upgrade plugins tool.
Example in Docker
Download example:
curl https://gitlab.nic.cz/websites/django-cms-qe/-/archive/master/django-cms-qe.zip?path=example --output example.zip
Unzip and go to the example folder:
unzip example.zip
cd django-cms-qe*/example/
Build the site image:
docker compose build
Run website in docker:
docker compose up -d
See the website at http://localhost:8000/. Login into http://localhost:8000/admin/ as username admin with password admin.
To run on a different port, specify the PORT parameter:
PORT=8008 docker compose up -d
Please wait a moment before browsing the website. It takes a while for all migrations to be completed and data to be loaded. You can monitor the status of this process in the log:
docker compose logs -f web
Stop the website:
docker compose down
Metadata
Release files for django-cms-qe 4.8.4
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_cms_qe-4.8.4.tar.gz | 7.0 MB | Without provenance | Details for django_cms_qe-4.8.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_cms_qe-4.8.4-py3-none-any.whl | Python 3 | none | any | Details for django_cms_qe-4.8.4-py3-none-any.whl |
Total release size: 15.2 MB
Release files / django_cms_qe-4.8.4.tar.gz
| Download URL | django_cms_qe-4.8.4.tar.gz |
|---|---|
| Size | 7.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10d29e4eb81cc8162cf2bc3c8f76f5c374e31a688aaa5a9f9265212a08e51dcf
|
|
BLAKE2b-256 checksum How to use checksums |
807750db2eb5419883ee5c318c43c0c43420535f590904c9edb87a0c19213164
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Release files / django_cms_qe-4.8.4-py3-none-any.whl
| Download URL | django_cms_qe-4.8.4-py3-none-any.whl |
|---|---|
| Size | 8.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ed2336ef6b92409cae29a661ff089d72473696a28e6c6a5568dafcf16c39371
|
|
BLAKE2b-256 checksum How to use checksums |
c7ecb6b4baa21a79a6b4664b360a35db49a502e7dc64aabbe504bc0b42542449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Security for django-cms-qe 4.8.4
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.