IPFS storage backend for Django.
Uploads are added and pinned to the configured IPFS node, which returns the IPFS Content ID (a hash of the contents). This hash is the name that is saved to your database. Duplicate content will also have the same address, saving disk space.
Because of this only file creation and reading is supported.
Other IPFS users access and reseed a piece of content through its unique content ID. Differently-distributed (i.e. normal HTTP) users can access the uploads through an HTTP→IPFS gateway.
pip install django-ipfs-storage
By default ipfs_storage adds and pins content to an IPFS daemon running on localhost and returns URLs pointing to the public https://ipfs.io/ipfs/ HTTP Gateway
To customise this, set the following variables in your settings.py:
- IPFS_STORAGE_API_URL: defaults to 'http://localhost:5001/api/v0/'.
- IPFS_GATEWAY_API_URL: defaults to 'https://ipfs.io/ipfs/'.
Set IPFS_GATEWAY_API_URL to 'http://localhost:8080/ipfs/' to serve content through your local daemon’s HTTP gateway.
There are two ways to use a Django storage backend.
As default backend
Use IPFS as Django’s default file storage backend:
# settings.py DEFAULT_FILE_STORAGE = 'ipfs_storage.InterPlanetaryFileSystemStorage' IPFS_STORAGE_API_URL = 'http://localhost:5001/api/v0/' IPFS_STORAGE_GATEWAY_URL = 'http://localhost:8080/ipfs/'
For a specific FileField
Alternatively, you may only want to use the IPFS storage backend for a single field:
from django.db import models from ipfs_storage import InterPlanetaryFileSystemStorage class MyModel(models.Model): # … file_stored_on_ipfs = models.FileField(storage=InterPlanetaryFileSystemStorage()) other_file = models.FileField() # will still use DEFAULT_FILE_STORAGE
Don’t forget the brackets to instantiate InterPlanetaryFileSystemStorage() with the default arguments!
Not my department. See https://ipfs.io/#why.
How do I ensure my uploads are always available?
How do I backup my uploads?
How do I delete an upload?
Because of the distributed nature of IPFS, anyone who accesses a piece of content keeps a copy, and reseeds it for you automatically until it’s evicted from their node’s local cache. Yay bandwidth costs! Boo censorship!
Unfortunately, if you’re trying to censor yourself (often quite necessary), this means the best we can do is unpin the piece of content from your own IPFS node(s) and hope nobody else has pinned it.
How do I securely expose my IPFS daemon’s API to connect remotely?
Someone please tell me.
How do I securely expose my own IPFS←HTTP Gateway?
Again, see above.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size django_ipfs_storage-0.0.4-py2.py3-none-any.whl (6.7 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size django-ipfs-storage-0.0.4.tar.gz (4.3 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for django_ipfs_storage-0.0.4-py2.py3-none-any.whl
Hashes for django-ipfs-storage-0.0.4.tar.gz