A self-hosted file sharing server with a simple command-line interface, supporting multiple storage backends.
transfer.sh is a self-hosted file sharing server that enables users to upload and share files via simple curl commands. It solves the problem of quickly transferring files between systems without relying on third-party cloud services, offering control over storage backends and security settings.
Developers, system administrators, and teams who need a private, controllable file sharing solution integrated into their workflow, especially those comfortable with command-line tools and self-hosting.
Developers choose transfer.sh for its simplicity, flexibility in storage providers, and the ability to self-host, ensuring data privacy and avoiding vendor lock-in. Its lightweight design and Docker support make deployment straightforward.
Easy and fast file sharing from the command-line.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports local file system, Amazon S3, Google Drive, and Storj, allowing integration with existing cloud infrastructure as detailed in the provider configuration options.
Upload and download files using standard curl commands with a straightforward API, making it easy to embed in scripts and automate workflows, exemplified in the usage examples.
Offers server-side encryption via headers, virus scanning with VirusTotal, and configurable access controls like IP whitelisting, as shown in the security settings and request headers.
Provides official Docker images with non-root variants for secure, easy deployment across environments, including detailed tags and build options in the Docker section.
Requires managing numerous environment variables and flags for storage, security, and server settings, which can be overwhelming for quick deployments without automation.
Lacks a rich front-end for file management; it's primarily command-line focused, making it less accessible for users who prefer GUI-based interactions.
Users must handle their own server updates, backups, and scaling, as emphasized in the disclaimer advising against relying on public instances.