django-chunk-upload 2.0.0

Demo

If you want to see a very simple Django demo project using this module, please take a look at django-chunk-upload-demo.

Installation

Install via pip:

pip install django-chunk-upload

And then add it to your Django INSTALLED_APPS:

INSTALLED_APPS = (
    # ...
    'django_chunk_upload',
)

Typical usage

1. An initial POST request is sent to the url linked to ChunkUploadView (or any subclass) with the first chunk of the file. The name of the chunk file can be overriden in the view (class attribute field_name). Example:

{"my_file": <File>}

2. In return, server with response with the upload_id, the current offset and the when will the upload expire (expires). Example:

{
    "upload_id": "5230ec1f59d1485d9d7974b853802e31",
    "offset": 10000,
    "expires": "2013-07-18T17:56:22.186Z"
}

3. Repeatedly POST subsequent chunks using the upload_id to identify the upload to the url linked to ChunkUploadView (or any subclass). Example:

{
    "upload_id": "5230ec1f59d1485d9d7974b853802e31",
    "my_file": <File>
}

4. Server will continue responding with the upload_id, the current offset and the expiration date (expires).

5. Finally, when upload is completed, a POST request is sent to the url linked to ChunkUploadCompleteView (or any subclass). This request must include the upload_id and the md5 checksum (hex). Example:

{
    "upload_id": "5230ec1f59d1485d9d7974b853802e31",
    "md5": "fc3ff98e8c6a0d3087d515c0473f8677"
}

6. If everything is OK, server will response with status code 200 and the data returned in the method get_response_data (if any).

Settings

Add any of these variables into your project settings to override them.

Support

If you find any bug or you want to propose a new feature, please use the issues tracker. I’ll be happy to help you! :-)