4df66415d6 | ||
---|---|---|
.hooks | ||
.infra | ||
cmd/tusd | ||
consullocker | ||
filestore | ||
limitedstore | ||
memorylocker | ||
prometheuscollector | ||
s3store | ||
uid | ||
vendor/github.com | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
LICENSE.txt | ||
Makefile | ||
README.md | ||
appveyor.yml | ||
composer.go | ||
composer.mgo | ||
composer_test.go | ||
concat_test.go | ||
config.go | ||
config_test.go | ||
cors_test.go | ||
datastore.go | ||
doc.go | ||
get_test.go | ||
handler.go | ||
handler_test.go | ||
head_test.go | ||
log.go | ||
metrics.go | ||
options_test.go | ||
patch_test.go | ||
post_test.go | ||
terminate_test.go | ||
unrouted_handler.go |
README.md
tusd
tus is a protocol based on HTTP for resumable file uploads. Resumable means that an upload can be interrupted at any moment and can be resumed without re-uploading the previous data again. An interruption may happen willingly, if the user wants to pause, or by accident in case of an network issue or server outage.
tusd is the official reference implementation of the tus resumable upload protocol. The protocol specifies a flexible method to upload files to remote servers using HTTP. The special feature is the ability to pause and resume uploads at any moment allowing to continue seamlessly after e.g. network interruptions.
Protocol version: 1.0.0
Getting started
Download pre-builts binaries (recommended)
You can download ready-to-use packages including binaries for OS X, Linux and Windows in various formats of the latest release.
Compile from source
Requirements:
- Go (1.3 or newer)
Running tusd from source:
Clone the git repository and cd
into it.
git clone git@github.com:tus/tusd.git
cd tusd
Now you can run tusd:
go run cmd/tusd/main.go
Using tusd manually
Besides from running tusd using the provided binary, you can embed it into your own Go program:
package main
import (
"github.com/tus/tusd"
"github.com/tus/tusd/filestore"
"net/http"
)
func main() {
// Create a new FileStore instance which is responsible for
// storing the uploaded file on disk in the specified directory.
// If you want to save them on a different medium, for example
// a remote FTP server, you can implement your own storage backend
// by implementing the tusd.DataStore interface.
store := filestore.FileStore{
Path: "./uploads",
}
// A storage backend for tusd may consist of multiple different parts which
// handle upload creation, locking, termination and so on. The composer is a
// place where all those seperated pieces are joined together. In this example
// we only use the file store but you may plug in multiple.
composer := tusd.NewStoreComposer()
store.UseIn(composer)
// Create a new HTTP handler for the tusd server by providing a configuration.
// The StoreComposer property must be set to allow the handler to function.
handler, err := tusd.NewHandler(tusd.Config{
BasePath: "files/",
StoreComposer: composer,
})
if err != nil {
panic("Unable to create handler: %s", err)
}
// Right now, nothing has happened since we need to start the HTTP server on
// our own. In the end, tusd will start listening on and accept request at
// http://localhost:8080/files
http.Handle("files/", http.StripPrefix("files/", handler))
err = http.ListenAndServe(":8080", nil)
if err != nil {
panic("Unable to listen: %s", err)
}
}
Please consult the online documentation for more details about tusd's APIs and its sub-packages.
Implementing own storages
The tusd server is built to be as flexible as possible and to allow the use
of different upload storage mechanisms. By default the tusd binary includes
filestore
which will save every upload
to a specific directory on disk.
If you have different requirements, you can build your own storage backend
which will save the files to S3, a remote FTP server or similar. Doing so
is as simple as implementing the tusd.DataStore
interface and using the new struct in the configuration object.
Please consult the documentation about detailed information about the
required methods.
Packages
This repository does not only contain the HTTP server's code but also other useful tools:
- s3store: A storage backend using AWS S3
- filestore: A storage backend using the local file system
- memorylocker: An in-memory locker for handling concurrent uploads
- consullocker: A locker using the distributed Consul service
- limitedstore: A storage wrapper limiting the total used space for uploads
Running the testsuite
go test -v ./...
License
This project is licensed under the MIT license, see LICENSE.txt
.