Installation
$ [sudo] pip install django-static-s3
$ [sudo] npm i -g django-static-s3
How it works
static/ hard-coded folder
scripts:
- create full-access user and credentials
- upload
static/
hard-coded environment variables names:
AWS_S3_STATIC_BUCKETAWS_S3_STATIC_USERAWS_S3_STATIC_ACCESS_KEY_IDAWS_S3_STATIC_SECRET_ACCESS_KEY
Examples
Makefile, create env
STATIC_BUCKET:=BUCKET_NAME
all:
test -s .env.s3.static || static-s3-create-env $(STATIC_BUCKET) > .env.s3.static
upload static/ to S3
export DJANGO_SETTINGS_MODULE=settings.dev
python manage.py collectstatic --no-input
set -o allexport
. .env.s3.static || exit
static-s3-upload
1 maintainer
Metadata
1 maintainer
Release files for django-static-s3 2020.12.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 | |
|---|---|---|---|---|
| django-static-s3-2020.12.3.tar.gz | 2.7 kB | Without provenance | Details |
Release files / django-static-s3-2020.12.3.tar.gz
| Download URL | django-static-s3-2020.12.3.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a76f43f9bba05ea03edd87cf0e9d9813beae5454bb8c690103adef0396902963
|
|
BLAKE2b-256 checksum How to use checksums |
aef045d490570da4392cbb588e4224e4e2bc4cfcbc846cbbe847c6bdaecfa3f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.0 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.6
|
Security for django-static-s3 2020.12.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.
