django-serve
A gunicorn based django runserver command.
Install
python3 -m pip install django-serve
and add to INSTALLED_APPS
#!python
INSTALLED_APPS = [
...
"django_serve.apps.ServeConfig",
...
]
Usage
./manage.py serve
options
--addrThe socket address to bind [default=127.0.0.1]--portThe socket port to bind [default=8000]--workersThe number of worker processes for handling requests [default max(1, (cpu + 1) / 2)]--nameA base to use with setproctitle for process naming [default=django]--wsgiDotted path to wsgi application [default=settings.WSGI_APPLICATION]--configThe Gunicorn config file [default=None]--log-levelThe granularity of Error log outputs (debug, info, warning, error, critical) [default=info]--logformatThe access log format (default='"%(m)s %(U)s%(q)s %(H)s" %(s)s %(B)s' same as default django runserver)--logger-classThe logger you want to use to log events [default=gunicorn_color.Logger if installed else gunicorn default one]--reload-engineWhich reload engine to use between polling or inotify (or not at all) [default=auto]
CHANGES
0.3.0
- add LOG_LEVEL env support
- add WORKERS env support
- drop Django < 3.2 support
- add Django 4.0 and 4.1 support
- drop Python < 3.8 support
- add Python 3.11 support
- update isort and flake8 config
- add rule for
__future__annotations
0.2.0
- use black
- drop Python 3.5 support
- add Django 3.2 support
- add Python 3.9 and 3.10 support
- add django-serve command
- add support for python -m django_serve
- install inotify only on linux platform
- add --reload-engine and DJANGO_DEFAULT_RELOAD_ENGINE option
- update default workers count
0.1.1
- add gunicorn-color as required
0.1.0
- initial implementation
- add support for gunicorn config file
- add custom django reloader
- add log-level option
- add logformat configuration
- add logger-class option
Metadata
Release files for django-serve 0.3
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-serve-0.3.tar.gz | 7.5 kB | Without provenance | Details for django-serve-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_serve-0.3-py3-none-any.whl | Python 3 | none | any | Details for django_serve-0.3-py3-none-any.whl |
Total release size: 19.9 kB
Release files / django-serve-0.3.tar.gz
| Download URL | django-serve-0.3.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4bfb79cb779dcdd50bf4c7ec6f0df9e80246980e483b02824107c80f9408e33b
|
|
BLAKE2b-256 checksum How to use checksums |
6efd663551188c99f175152e1436cc0c5bb22807a96c0a1a12a7d177ec7562fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / django_serve-0.3-py3-none-any.whl
| Download URL | django_serve-0.3-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2ab66f18b4a87f8cf0041d4aa848789df40e05efc58457eba4d65f1a4725015
|
|
BLAKE2b-256 checksum How to use checksums |
52c08d006a8c6ad2774fd2cdccd3b431221f4911833eed84a194e04199a1ba00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for django-serve 0.3
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.