Package client provides a convenient HTTP client with support for common operations like GET, POST, PUT, PATCH, DELETE, file uploads, compression, and progress tracking.
Package facebook is a Go library fully supports Facebook Graph API (both 1.0 and 2.x) with file upload, batch request, FQL and multi-FQL.
Package facebook is a Go library fully supports Facebook Graph API with file upload and batch request.
Package uplink is the main entrypoint to interacting with Storj Labs' decentralized storage network. Sign up for an account on a Satellite today! https://storj.io/ The fundamental unit of access in the Storj Labs storage network is the Access Grant. An access grant is a serialized structure that is internally comprised of an API Key, a set of encryption key information, and information about which Storj Labs or Tardigrade network Satellite is responsible for the metadata. An access grant is always associated with exactly one Project on one Satellite. If you don't already have an access grant, you will need make an account on a Satellite, generate an API Key, and encapsulate that API Key with encryption information into an access grant. If you don't already have an account on a Satellite, first make one at https://storj.io/ and note the Satellite you choose (such as us1.storj.io, eu1.storj.io, etc). Then, make an API Key in the web interface. The first step to any project is to generate a restricted access grant with the minimal permissions that are needed. Access grants contains all encryption information and they should be restricted as much as possible. To make an access grant, you can create one using our Uplink CLI tool's 'share' subcommand (after setting up the Uplink CLI tool), or you can make one as follows: In the above example, 'serializedAccess' is a human-readable string that represents read-only access to just the "logs" bucket, and is only able to decrypt that one bucket thanks to hierarchical deterministic key derivation. Note: RequestAccessWithPassphrase is CPU-intensive, and your application's normal lifecycle should avoid it and use ParseAccess where possible instead. To revoke an access grant see the Project.RevokeAccess method. A common architecture for building applications is to have a single bucket for the entire application to store the objects of all users. In such architecture, it is of utmost importance to guarantee that users can access only their objects but not the objects of other users. This can be achieved by implementing an app-specific authentication service that generates an access grant for each user by restricting the main access grant of the application. This user-specific access grant is restricted to access the objects only within a specific key prefix defined for the user. When initialized, the authentication server creates the main application access grant with an empty passphrase as follows. The authentication service does not hold any encryption information about users, so the passphrase used to request the main application access grant does not matter. The encryption keys related to user objects will be overridden in a next step on the client-side. It is important that once set to a specific value, this passphrase never changes in the future. Therefore, the best practice is to use an empty passphrase. Whenever a user is authenticated, the authentication service generates the user-specific access grant as follows: The userID is something that uniquely identifies the users in the application and must never change. Along with the user access grant, the authentication service should return a user-specific salt. The salt must be always the same for this user. The salt size is 16-byte or 32-byte. Once the application receives the user-specific access grant and the user-specific salt from the authentication service, it has to override the encryption key in the access grant, so users can encrypt and decrypt their files with encryption keys derived from their passphrase. The user-specific access grant is now ready to use by the application. Once you have a valid access grant, you can open a Project with the access that access grant allows for. Projects allow you to manage buckets and objects within buckets. A bucket represents a collection of objects. You can upload, download, list, and delete objects of any size or shape. Objects within buckets are represented by keys, where keys can optionally be listed using the "/" delimiter. Note: Objects and object keys within buckets are end-to-end encrypted, but bucket names themselves are not encrypted, so the billing interface on the Satellite can show you bucket line items. Objects support a couple kilobytes of arbitrary key/value metadata, and arbitrary-size primary data streams with the ability to read at arbitrary offsets. If you want to access only a small subrange of the data you uploaded, you can use `uplink.DownloadOptions` to specify the download range. Listing objects returns an iterator that allows to walk through all the items:
Package httpin helps decoding an HTTP request to a custom struct by binding data with querystring (query params), HTTP headers, form data, JSON/XML payloads, URL path params, and file uploads (multipart/form-data).
Package log4go provides named structured loggers, a slog handler, daily log files and asynchronous uploads compatible with xilore-log4j.
Package wildcsv reads delimited text that the calling program did not produce: a customer upload, a spreadsheet export, a bank statement, a file handed to a coding agent.
Package imaging resizes and re-encodes images in pure Go, safely enough to run on user uploads: it checks an image's dimensions from its header before decoding it (a 1 KB file can declare a 100,000 × 100,000 image and exhaust memory when decoded), applies the EXIF orientation phones write, and re-encodes every output, which drops EXIF, GPS and any payload smuggled in the original.
Package drive implements bounded Google Drive operations: name-based file search, file metadata reads, bounded text reads, and duplicate-safe uploads.
git-lfs-chunked is a Git LFS custom transfer agent that moves objects as content-defined chunks, so that after a large file is edited only the changed chunks are uploaded or downloaded.
Package onedrive implements bounded Microsoft Graph file operations for OneDrive and SharePoint document libraries: name-based search, item metadata reads, bounded text reads, and uploads and folder creation that converge on one item when a Step is dispatched twice.
Package drive implements bounded Google Drive operations: name-based file search, file metadata reads, bounded text reads, and duplicate-safe uploads.
Package thoa is a Go port of the dataset (data lake) parts of the thoa CLI (https://pypi.org/project/thoa/, ported from 0.1.8): upload local files as a dataset, download a dataset by id.
Package storage provides object storage for application files: upload, download, delete, and the two ways of handing a client a link to an object.
Package onedrive implements bounded Microsoft Graph file operations for OneDrive and SharePoint document libraries: name-based search, item metadata reads, bounded text reads, and uploads and folder creation that converge on one item when a Step is dispatched twice.
Package colimity provides typed file APIs and bounded direct multipart uploads.
Package kompressr uploads, manages and delivers files through Kompressr.
Package imagemagick contains an example of using ImageMagick to process a file uploaded to Cloud Storage.
Package conan implements the Conan 2.x repository protocol: ping, auth, search, recipe/package revision metadata, file get/put, upload_urls, download via pull-through proxy.
Package cairnmark is the official Go client for the CairnMark file service: streaming uploads and downloads, presigned-URL retrieval, tag search with lazy pagination, client-side checksum verification, archive extraction as a job you can wait on or poll, and safe retries.
Package ocdav implements a WebDAV server handler module for Caddy that honours the X-OC-Mtime header, so a file arrives with the time it was written rather than the time it was uploaded.
Package facebook is a Go library fully supports Facebook Graph API (both 1.0 and 2.x) with file upload, batch request, FQL and multi-FQL. It can be used in Google App Engine. Library design is highly influenced by facebook official PHP/JS SDK. If you have experience with PHP/JS SDK, you may feel quite familiar with it. Go to project home page to see samples. Link: https://github.com/huandu/facebook This library doesn't implement any deprecated old RESTful API. And it won't.
This is a Go library fully supports Facebook Graph API (both 1.0 and 2.x) with file upload, batch request, FQL and multi-FQL.
Package bigoci uploads and downloads large files to and from OCI registries.
Package client implements a client library for OTS supporting the OTSMeta content format for file upload support.
Command gdrive-backup uploads a directory or a single file to one Google Drive folder through a configured rclone remote.