django backblaze b2 storage using b2sdk (can be used outside of django for upload/download single files too)
Install the last stable release
pip install django-b2
Create bucket at backblaze.com. No need for older versions of saved files: While royendgel/django-backblazeb2-storage uses older versions, django-b2 will always rename to unique filename.
Add this to Django settings
MEDIA_URL = '/media/' DEFAULT_FILE_STORAGE = 'django_b2.storage.B2Storage' # if used without django-tenant-schemas # DEFAULT_FILE_STORAGE = 'django_b2.tenant_storage.TenantB2Storage' # if used with django-tenant-schemas (django-tenants: see notice in code) B2_APP_KEY_ID = 000xxxxxxxxxxxx000000000n B2_APP_KEY = keyvalue B2_BUCKET_NAME = bucketname # see bellow: B2_FORCE_UNIQUE = False | True # for v0.7, True is default # optional, see bellow: MEDIA_ROOT = .. B2_LOCAL_MEDIA = .. # "", "M", "L", "ML"
Of course B2_.. values (..KEY..) should never be published. Don't upload the settings file to public sites (github, ..) or use some technique to hide the secret parameters. This can be environment variables or hidden config file. You can see tests/test_B2Storage.py for ideas.
Upload library which enforces name uniqueness
django_b2 saves each file into unique folder ie. as /name. This should prevent problems with non unique names. If this doesn't work properly in your case especially if other tool makes the same thing you should turn this feature off. Example: django_drf_filepond creates similar uniquely named folders. In such case set
B2_FORCE_UNIQUE = False
We recommend set this always (False|True) because the default could change in the future.
Imagekit which need reopen the picture soon (Wagtail?), local filesystem cache
If you upload an image and the imagekit want to reopen it immediately (to create thumbnails or so) it can fail because backblaze storage has the file not immediately accessible. We handle this that way that you can add B2_LOCAL_MEDIA into your settings.
B2_LOCAL_MEDIA = 'ML'
M means that the copy of file is saved to the local filesystem MEDIA_ROOT too and the file is opened from this local "cache". That way the files are soon and faster accessible. L means that a log files are written into <MEDIA_ROOT>/_log. With help of logs (files in _log directory) the locally cached files can be deleted: one hour later or 5 days later.
There is a script (django management command) b2_clear_local_media usable via cron, celery,.. It will delete local media files older than few hours or days. Later they will be served from backblaze.
Using outside of Django
Don't use the storage.py file. Use the backblaze_b2.py only.
from django_b2.backblaze_b2 import BackBlazeB2 b2 = BackBlazeB2() b2.authorize("production", application_key_id, application_key) b2.set_bucket(bucket_name) with open(filename, 'rb') as f: b2.upload_file(filename, f) content = b2.download_file(filename) with open(filename2, 'wb') as f: f.write(content)
Nginx large file uploads: You need at least modify /etc/nginx/nginx.conf, http section, add client_... settings.
client_max_body_size 100M; client_body_buffer_size 100M; client_body_timeout 120;
Upload (backup) single file (new in 0.2.0)
This is implemented in backblaze_b2.py file if called as script. We don't implement it (yet) as the django management command. That means outside of Django: You can use this too. And in Django: No need (at 0.2.0) to add this package to INSTALLED_APPS.
You can describe the target bucket in environment variables or in the .ini file. For details:
python (path/)backblaze_b2.py --help
Backup the postgres database (new in 0.2.0)
Once django-b2 is installed, pgtob2.sh script is available in the virtual environment. Write 'which pgtob2.sh' for its location. See comments inside the script for more info.
More (this is not well tested)
django-tenants instead of django-tenant-schemas? Maybe it could work but the mixin is inside the django-tenant-schemas package. Add django-tenant-schemas into requirements too but don't add it into INSTALLED_APPS/SHARED_APPS.
storage=B2Storage() in models, turn it off during tests. See https://github.com/pyutil/django-b2/issues/4 To work as real B2Storage, 'B2Storage' string must be contained in settings.DEFAULT_FILE_STORAGE. Otherwise DEFAULT_FILE_STORAGE will be instantiated. This makes following in tests possible: @override_settings(DEFAULT_FILE_STORAGE='django.core.files.storage.FileSystemStorage')
Upload and Download methods work, but probably very stupid and non-effective. If you understand the problem more, please help rewrite them and send pull request:
- fork pyutil/django-b2,
- clone your fork,
- set upstream in git config to pyutil/,
- arrange virtual environment and install (pip install -r ...) requirements.txt & requirements_dev.txt,
- don't touch "master" branch so you can always pull pyutil/ upstream,
- create a "fork" branch where you can always merge "master" and feature branches,
- create a "" branch(es) for every single change,
- commit+push "" branch,
- in github web interface generate a pull request,
- merge "" branch into "fork" branch (optional) (maybe you have better idea how to arrange branches in your fork)
Install test requirements inside your virtual environment
pip install -r requirements_test.txt
Create a backblaze bucket. Set B2_.. environment variables or a config file /etc/django/test-django-b2/env.ini - see tests/test_B2Storage.py. Run pytest. Alternatively you can run tox: You could install pyenv system-wide, pyenv install required 3.N python versions (see tox.ini). Then in the project dir: pyenv local 3.x.x 3.y.y 3.z.z And run: tox