Django-livereload
Application performing a LiveReload with tiny-lr once the development server is ready.
Why this project ?
I recently started using Gulp and LiveReload to automatize some tasks. Everytime an HTML, CSS or JS file changes, a livereload is performed in the browser to reflect those changes, and I was pretty happy with that.
But I found one limitation, I cannot perform a livereload of the current page when editing Python files because the development server provided by Django is not necessary ready as soon as the livereload request is emitted.
That’s why I created this application.
Installation
First install the package on your system:
$ pip install django-livereload
Then register the 'livereload' application in your INSTALLED_APPS setting, before the 'django.contrib.staticfiles' application if used.
Usage
If the livereload server provided by tiny-lr is launched (via Gulp, Grunt or whatever), the runserver command will do a livereload on your browser whenever the Django development server is ready.
The script
If you want to livereload-js script injected into your pages because you don’t want to deal with a plug-in, simply register this middleware in your project: 'livereload.middleware.LiveReloadScript'.
Metadata
Release files for django-livereload 1.7
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-livereload-1.7.tar.gz | 4.6 kB | Without provenance | Details for django-livereload-1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_livereload-1.7-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for django_livereload-1.7-py2.py3-none-any.whl |
Total release size: 11.1 kB
Release files / django-livereload-1.7.tar.gz
| Download URL | django-livereload-1.7.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e660863a2901cbda49bbc858f5a890791329453eb4743f2b57aa8a7cd35148e
|
|
BLAKE2b-256 checksum How to use checksums |
f64dc5016aead5fc60ffb54cb6f3281b1527aa44d24f918b02f3307371f5e61d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_livereload-1.7-py2.py3-none-any.whl
| Download URL | django_livereload-1.7-py2.py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b64bb1fc8fa9a99c2386a180d5723bf18024c66174f7d33d5071b628ba029e83
|
|
BLAKE2b-256 checksum How to use checksums |
12e1e826b31c10604ca237c460c940b697f029f5afe8a61ba34b3f5301b2eebd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-livereload 1.7
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.