the intention of this application is to enable static app files (css, js, pics) in the app folder itself.
<application1>/media/<application1>/js/script.js <application2>/media/<application2>/js/script.js
<project>/media/logo.jpg
To use this view in development you should add something like the following to urls.py: if settings.DEBUG: urlpatterns += (r’^media/(?P<path>.*)$’, ‘site.media.serve_apps’, {‘document_root’ : settings.MEDIA_ROOT})
For deployment there is a managament command called symlinkmedia that will create symlinks to each applications media directory in MEDIA_ROOT.
Now all apps in INSTALLED_APPS that have a “media” directory in them will be reachable as ‘/media/<application_name>/’.
You can then have the admin media files served by setting ADMIN_MEDIA_PREFIX = ‘/media/admin/’
1 maintainer
Metadata
1 maintainer
Release files for django-appmedia 1.0.1
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-appmedia-1.0.1.tar.gz | 25.3 kB | Without provenance | Details for django-appmedia-1.0.1.tar.gz |
Release files / django-appmedia-1.0.1.tar.gz
| Download URL | django-appmedia-1.0.1.tar.gz |
|---|---|
| Size | 25.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c41cb355f10436a9c811ede7495b4088f785ea88a779fd6fb669ee2eb7cb4697
|
|
BLAKE2b-256 checksum How to use checksums |
f963f5d9d04e0eea193bada59f2500b45053f500bd546d9094d5e68bc78f86b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-appmedia 1.0.1
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.
