Delete unused media files from Django project
Package provides management command cleanup_unused_media for Django applications.
You can remove all not used media files (files without references from any Django model with FileField or ImageField fields or their inheritances).
Installation
Install django-unused-media: pip install django-unused-media
Python 2.7, 3.6, 3.7, pypy are tested with tox.
Django 1.8, 1.9, 1.10, 1.11, 2.0, 2.1, 2.2, 3.0 are tested with tox.
Add django-unused-media to INSTALLED_APPS: python INSTALLED_APPS = ( ... 'django_unused_media', ... )
Usage
To cleanup all unused media files, run management command:
./manage.py cleanup_unused_media
By default command is running in interactive mode. List of files which are going to be removed will be displayed for confirmation. User has to confirm the action.
Options
--noinput, --no-input
Non interactive mode. Command will remove files without any confirmation from the user. Useful for scripts.
./manage.py cleanup_unused_media --noinput
-e, --exclude
To avoid operating on particular files you can use exclude option. - ``*`` as any symbol is supported. - Can use multiple options in one command.
For example, to keep .gitignore and *.png files you can use:
./manage.py cleanup_unused_media -e *.gitignore -e *.png
Also you can exclude entire folder or some files in that folder (path should be relative to settings.MEDIA_ROOT):
./manage.py cleanup_unused_media -e path/to/dir/* -e path/to/dir/my*.doc
--minimum-file-age, seconds
Default = 60 (one minute)
Minimum file age to consider for cleanup. All files younger this age will be skipped.
--remove-empty-dirs
By default script keeps empty dirs in media folder. But with this option all empty directories will be removed after cleaning process automatically.
--dry-run
Dry run without any affect on your data
--verbosity {0,1,2}, -v {0,1,2}
Verbosity level. - 0 - silent - 1 - normal output (default) - 2 - verbose output (list individual files)
Tests
At first make sure that you are in virtualenv if you use it.
Install all dependencies:
make setup
To run tests:
make test
To run static analyser:
make flake8
License
1 maintainer
Metadata
1 maintainer
Release files for django-unused-media 0.2.2
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-unused-media-0.2.2.tar.gz | 6.3 kB | Without provenance | Details for django-unused-media-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_unused_media-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for django_unused_media-0.2.2-py3-none-any.whl |
Total release size: 18.4 kB
Release files / django-unused-media-0.2.2.tar.gz
| Download URL | django-unused-media-0.2.2.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f46b5a7d3e10f09e31126aefb2efe24e3dedb6a89daf786f7e055c5298668ee
|
|
BLAKE2b-256 checksum How to use checksums |
285b58598b4397cf1d5480206c34a0baa201e782627c079cb208369a3a855f00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.7
|
Release files / django_unused_media-0.2.2-py3-none-any.whl
| Download URL | django_unused_media-0.2.2-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
390d0cfa4ac9e4d0c4de0878b42bda41ed188fa62b0032fdf0a266e7136ce013
|
|
BLAKE2b-256 checksum How to use checksums |
4948b8ca3f24a7df20718456c3d7630f4bbfa1017f19d64d50d9d1d3282e697a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.7
|
Security for django-unused-media 0.2.2
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.
