Django Bower App
Library to manage bower.json dependancies with ease
WHY
Managing assets for django is more and more complicated when you need to interact with heavy javascript page. Now many javascripts developers use bower to manger their dependancies.
Bower then need to be interfaced with Django as seemlessly as possible. Neither the javascript developer nor the django developper must change the way they work.
django-bower-app aims to be the glue between javascript and django with simple, easy to manage code.
HOW
A simple command, bower_install will look in each of the static directory of each app and extract the bower.json, letting bower_components untouched and build each module dependancies in the settings.STATIC_ROOT directory.
You can now develop your javascript apps with bower and create a production ready environnment with bower_install
Requirements
Obviousely, to run django-bower-app, you need bower and django. That’s all.
INSTALL
First download this module and install it with
>>> python setup.py install
Then add “djangobwr” to your INSTALLED_APPS
>>> INSTALLED_APPS = ( ... "djangobwr", ... )
you are ready to run the command each time you want to collect the bower dependancies:
>>> python manage.py bower_install
Metadata
Release files for django-bower-app 0.5
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-bower-app-0.5.zip | 7.9 kB | Without provenance | Details |
Release files / django-bower-app-0.5.zip
| Download URL | django-bower-app-0.5.zip |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eaeb8dd3346a9db86bbffe4ced87d4380b0540ed09ec708acf9d58ca043f9b96
|
|
BLAKE2b-256 checksum How to use checksums |
0c8633e08a443e630644a032e19ae3ef7bddb7c55e62947d600855f0c901bd75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-bower-app 0.5
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.