Django Static LoR
LoR as “Local or Remote” is a useful tool for manage static files between testing and production.
Install
Install the package on your system:
pip install django-static-lor
Make the following things in your settings.py:
Add lor app at the beginning of your INSTALLED_APPS
Add LOR_USE_LOCAL_URLS for define if you want local or remote URLs (Better is simply LOR_USE_LOCAL_URLS = DEBUG
Add LOR_STATIC_DIR for define where is the app’s static directory
Add LOR_STATIC_DIR in STATICFILES_DIRS if you want to serve it when DEBUG == False
Add you matches in LOR_FILES_URLS
Your settings will look like something like this:
INSTALLED_APPS = (
'lor',
...
)
LOR_USE_LOCAL_URLS = False
LOR_STATIC_DIR = '/my/lor/static/dir/'
STATICFILES_DIRS = (
...
LOR_STATIC_DIR,
)
LOR_FILES_URLS = {
'jquery': ('js/jquery.js',
'https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js')
}
Done!
Usage
In templates
{% load lor %}
My jQuery URL: {% lor_url 'jquery' %}
Collect remote files
./manage.py wget
This will download all files in LOR_FILES_URLS and put them in LOR_USE_LOCAL_URLS.
1 maintainer
Metadata
1 maintainer
Release files for django-static-lor 0.1.0
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-static-lor-0.1.0.tar.gz | 6.5 kB | Without provenance | Details for django-static-lor-0.1.0.tar.gz |
Release files / django-static-lor-0.1.0.tar.gz
| Download URL | django-static-lor-0.1.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a2f4499a94663dfeb7583240aa747c45faeef5683a1f6f56e5827eac734fca8
|
|
BLAKE2b-256 checksum How to use checksums |
6bd22c0b11fdc55d80f5a428fd2cd2cf5a0b2217bd54497f13cbf3153d688498
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-static-lor 0.1.0
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.
