ConcaterDataStore is the interface required to be implemented if the Concatenation extension should be enabled. Only in this case, the handler will pa

Config provides a way to configure the Handler depending on your needs.

ContentServerDataStore is the interface for DataStores that can serve content directly. When the handler serves a GET request, it will pass the reques

CorsConfig provides a way to customize the the handling of Cross-Origin Resource Sharing (CORS). More details about CORS are available at https://deve

DataStore is the base interface for storages to implement. It provides functions to create new uploads and fetch existing ones. Note: the context val

Error represents an error with the intent to be sent in the HTTP response to the client. Therefore, it also contains a HTTPResponse, next to an error

ErrorsTotalMap stores the counters for the different HTTP errors.

Event represents an event from tusd which can be handled by the application.

FileInfo contains information about a single upload resource.

FileInfo contains information about a single upload resource.

FileInfoChanges collects changes the should be made to a FileInfo object. This can be done using the PreUploadCreateCallback to modify certain propert

FileInfoChanges collects changes the should be made to a FileInfo struct. This can be done using the PreUploadCreateCallback to modify certain propert

See the handler.DataStore interface for documentation about the different methods.

See the handler.DataStore interface for documentation about the different methods.

go:generate mockgen -package handler_test -source utils_test.go -destination=handler_mock_test.go FullDataStore is an interface combining most interfa

GCSAPI is an interface composed of all the necessary GCS operations that are required to enable the tus protocol to work with Google's cloud storage.

GCSReader implements cloud.google.com/go/storage.Reader. It is used to read Google Cloud storage objects. TODO: Remain, Size, ContentType seem to only

GCSService holds the cloud.google.com/go/storage client as well as its associated context. Closures are used as minimal wrappers around the Google Clo

See the handler.DataStore interface for documentation about the different methods.

HTTPRequest contains basic details of an incoming HTTP request.

HTTPRequest contains basic details of an incoming HTTP request.

HTTPResponse contains basic details of an outgoing HTTP response.

HTTPResponse contains basic details of an outgoing HTTP response.

Handler is a ready to use handler with routing

HookEvent represents an event from tusd which can be handled by the application.

The hook service definition.

HookHandler is the main inferface to be implemented by all hook backends.

HookHandlerClient is the client API for HookHandler service. For semantics around ctx use and closing/ending streaming RPCs, please refer to https://

This is the implementation of plugin.Plugin so we can serve/consume this This has two methods: Server must return an RPC server for this plugin type.

Here is an implementation that talks over RPC

Here is the RPC server that HookHandlerRPC talks to, conforming to the requirements of net/rpc

HookHandlerServer is the server API for HookHandler service. All implementations must embed UnimplementedHookHandlerServer for forward compatibility

The hook service definition.

The hook service definition.

HookRequest contains the information about the hook type, the involved upload, and causing HTTP request.

HookRequest contains the information about the hook type, the involved upload, and causing HTTP request.

HookResponse is the response after a hook is executed.

HookResponse is the response after a hook is executed.

LengthDeferrerDataStore is the interface that must be implemented if the creation-defer-length extension should be enabled. The extension enables a cl

Lock is the interface for a lock as returned from a Locker.

Locker is the interface required for custom lock persisting mechanisms. Common ways to store this information is in memory, on disk or using an extern

MemoryLocker persists locks using memory and therefore allowing a simple and cheap mechanism. Locks will only exist as long as this object is kept in

Metrics provides numbers about the usage of the tusd handler. Since these may be accessed from multiple goroutines, it is necessary to read and modify

MockAzBlob is a mock of AzBlob interface.

MockAzBlobMockRecorder is the mock recorder for MockAzBlob.

MockAzService is a mock of AzService interface.

MockAzServiceMockRecorder is the mock recorder for MockAzService.

MockFullDataStore is a mock of FullDataStore interface.

MockFullDataStoreMockRecorder is the mock recorder for MockFullDataStore.

MockFullLock is a mock of FullLock interface.

MockFullLockMockRecorder is the mock recorder for MockFullLock.

MockFullLocker is a mock of FullLocker interface.

MockFullLockerMockRecorder is the mock recorder for MockFullLocker.

MockFullUpload is a mock of FullUpload interface.

MockFullUploadMockRecorder is the mock recorder for MockFullUpload.

MockGCSAPI is a mock of GCSAPI interface.

MockGCSAPIMockRecorder is the mock recorder for MockGCSAPI.

MockGCSReader is a mock of GCSReader interface.

MockGCSReaderMockRecorder is the mock recorder for MockGCSReader.

MockHookHandler is a mock of HookHandler interface.

MockHookHandlerMockRecorder is the mock recorder for MockHookHandler.

MockReader is an implementation of GCSReader.

MockS3API is a mock of S3API interface.

MockS3API is a mock of S3API interface.

MockS3APIMockRecorder is the mock recorder for MockS3API.

MockS3APIMockRecorder is the mock recorder for MockS3API.

Here is the implementation of our hook handler