Open Source Go File Transfer Protocol (FTP) Software

Inspired by MailCatcher, easier to install. Built with Go, MailHog runs without installation on multiple platforms. Run it from Docker Hub or using the provided Dockerfile. The SMTP server starts on port 1025, the HTTP server starts on port 8025, in-memory message storage. ESMTP server implementing RFC5321. Support for SMTP AUTH (RFC4954) and PIPELINING (RFC2920). Web interface to view messages (plain text, HTML or source). Supports RFC2047 encoded headers. Real-time updates using EventSource. Release messages to real SMTP servers. Chaos Monkey for failure testing. HTTP API to list, retrieve and delete messages. See APIv1 and APIv2 documentation for more information. HTTP basic authentication for MailHog UI and API. Multipart MIME support. Download individual MIME parts. In-memory message storage. MongoDB and file based storage for message persistence. Lightweight and portable. No installation required.

Yet another way to transfer files that strikes a good balance between speed, security or simplicity by using relay-assisted peer-to-peer transactions and end-to-end encryption via password-authenticated key exchange. There are a lot of ways to transfer files. Above the basic necessity of preserving the data during the transfer, sharing data should be fast, secure, and most of all, easy. Most file transfer utilities I’ve used encompass two thirds of these qualities. I’ve wanted to make a utility that encompasses all three, without compromising any one of them. A common way to transfer a file is to first upload data to a server, and then, once uploaded, the link is shared with someone who goes to download it. This method is easy, but slow, the transfer rate of the file is half the harmonic mean of the upload and download speeds which makes it slower than either just uploading or downloading.

qrcp binds a web server to the address of your Wi-Fi network interface on a random port and creates a handler for it. The default handler serves the content and exits the program when the transfer is complete. When used to receive files, qrcp serves an upload page and handles the transfer. Most QR apps can detect URLs in decoded text and act accordingly (i.e. open the decoded URL with the default browser), so when the QR code is scanned the content will begin downloading by the mobile browser. When sending multiple files at once, qrcp creates a zip archive of the files or folders you want to transfer, and deletes the zip archive once the transfer is complete. When receiving files, qrcp serves an “upload page” through which you can choose files from your mobile. The default configuration file is stored in $HOME/qrcp.json, however, you can specify the location of the config file by passing the --config flag.

OEM Software to access a wide range of backend. Code is available from https://github.com/mickael-kerjean/filestash

Distribyted is an alternative torrent client. It can expose torrent files as a standard FUSE mount or webDAV endpoint and download them on demand, allowing random reads using a fixed amount of disk space. Distribyted supports several ways to expose the files to the user or external applications. Applications that supports WebDAV can access torrent files using this protocol. It is recommended when distribyted is running in a remote machine or using docker. Distribyted can show some kind of files directly as folders, making it possible for applications to read only the parts that they need. Here is a list of supported, to-be-supported, and not supported formats. Play multimedia files on your favorite video or audio player. These files will be downloaded on demand and only the needed parts.