summaryrefslogtreecommitdiff
path: root/issues/gn-uploader/resume-upload.gmi
blob: ea564b84923a98bda264aff6ac2b7c47b67c0f3d (about) (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# gn-uploader: Resume Upload

## Tags

* status: open
* priority: medium
* assigned: fredm, flisso
* type: feature request, feature-request
* keywords: gn-uploader, uploader, upload, resume upload

## Description

If a user is uploading a particularly large file, we might need to provide a way for the user to resume their upload of the file.

Maybe this can wait until we have
=> /issues/gn-uploader/link-authentication-authorisation linked authentication/authorisation to gn-uploader.
In this way, each upload can be linked to a specific user.

### TODOs

* [x] Build UI to allow uploads
* [x] Build back-end to handle uploads
* [ ] Rework cancel to actually kill the upload
* [ ] Provide pause functionality
* [ ] Maybe trigger job on separate endpoint: cleaner and avoids
* [ ] Handle upload failures/errors
* [ ]
* [ ]
* [ ]
* [ ]

  .
  .
  .

* [ ] Deploy to staging

### Possible Resources

=> https://javascript.info/resume-upload
=> https://github.com/23/resumable.js/
=> https://www.dropzone.dev/
=> https://stackoverflow.com/questions/69339582/what-hash-python-3-hashlib-yields-a-portable-hash-of-file-contents