Upload Service

tl;dr¶

Debug Information

Image: docker.io/tusproject/tusd:v1.12

Ports: 1080/tcp
Prometheus: http://<hostname>:1080/api/upload/metrics
API: http://<hostname>:1080/api/upload

Overview¶

We use the TUS open protocol for resume-able file uploads which based entirely on HTTP. Even though the Upload Service is part of the standard installation, it is an entirely optional component and can be replaced with any S3-compatible Blob Storage.

Architecture¶

The Upload Service communicates internally with the Storage Service (c.f. Figure 1).

The Upload Service is responsible for uploading files (mainly CSV-files) into a Blob Storage that can be accesses trough the S3 protocol (e.g. our Storage Service). Make sure that the Upload Service can be accessed from the Gateway Service.

Limitations¶

No support for authentication.

Do you miss functionality? Do these limitations affect you?

We strongly encourage you to help us implement it as we are welcoming contributors to open-source software and get in contact with us, we happily answer requests for collaboration with attached CV and your programming experience!

Security¶

We strongly encourage to limit the clients allowed to upload by adding your subnet, e.g. 128.130.0.0/16 (=TU Wien subnet) to the Gateway Service configuration file like this:
dbrepo.conf
```
location /api/upload {
  allow 128.130.0.0/16;
  deny all;
  ...
}
```