Go IPFS alternatives and similar software solutions
Based on the "Distributed filesystems" category.
Alternatively, view Go IPFS alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
Firefox Send
DISCONTINUED. A file sharing experiment which allows you to send encrypted files to other users. -
SeaweedFS
DISCONTINUED. SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. [Moved to: https://github.com/seaweedfs/seaweedfs] -
-
Seafile
High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features. -
-
-
-
Filestash
:file_folder: A file manager / web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ... -
-
OnionShare
Securely and anonymously share files, host websites, and chat with friends using the Tor network -
Camlistore
Perkeep (née Camlistore) is your personal storage system for life: a way of storing, syncing, sharing, modelling and backing up content. -
-
-
-
SparkleShare
Share and collaborate by syncing with any Git repository instantly. Linux, macOS, and Windows. -
-
-
-
-
Magnetissimo
Web application that indexes all popular torrent sites, and saves it to the local database. -
DirectoryLister
📂 Directory Lister is the easiest way to expose the contents of any web-accessible folder for browsing and sharing. -
droppy
DISCONTINUED. droppy is a self-hosted cloud server with an interface similar to desktop file managers and has capabilites to edit files on-the-fly as well as view and playback media directly in the browser. -
Syncany
DISCONTINUED. Syncany is a cloud storage and filesharing application with a focus on security and abstraction of storage. -
-
Pydio
DISCONTINUED. Turn any web server into a powerful file management system and an alternative to mainstream cloud storage providers. -
-
-
-
-
-
ProjectSend
ProjectSend is a free, open source software that lets you share files with your clients, focused on ease of use and privacy. It supports clients groups, system users roles, statistics, multiple languages, detailed logs... and much more! -
Zipline
A ShareX/file upload server that is easy to use, packed with features, and with an easy setup! -
linx
DISCONTINUED. Self-hosted file/code/media sharing website. ~~~~~~~~~~~~~~~~~~~ Demo: https://demo.linx-server.net/ [Moved to: https://github.com/linx-server/linx-server] -
-
Samba
https://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub) -
-
-
-
-
-
-
Uguu
Uguu is a simple lightweight temporary file host with support for drop, paste, click and API uploading.
CodeRabbit: AI Code Reviews for Developers
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Go IPFS or a related project?
README
go-ipfs
What is IPFS?
IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from previous systems such as Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single BitTorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built-in. You can also mount the world at /ipfs.
For more info see: https://docs.ipfs.io/introduction/overview/
Before opening an issue, consider using one of the following locations to ensure you are opening your thread in the right place:
- go-ipfs implementation bugs in this repo.
- Documentation issues in ipfs/docs issues.
- IPFS design in ipfs/specs issues.
- Exploration of new ideas in ipfs/notes issues.
- Ask questions and meet the rest of the community at the IPFS Forum.
- Or chat with us.
Next milestones
<!-- ToDo automate creation of these
Table of Contents
- Security Issues
- Install
- System Requirements
- Docker
- Native Linux package managers
- ArchLinux
- Nix
- Solus
- openSUSE
- Other package managers
- Guix
- Snap
- macOS package managers
- MacPorts
- Nix
- Homebrew
- Windows package managers
- Chocolatey
- Scoop
- Install prebuilt binaries
- Build from Source
- Install Go
- Download and Compile IPFS
- Cross Compiling
- OpenSSL
- Troubleshooting
- Updating go-ipfs
- Getting Started
- Packages
- Development
- Contributing
- License
Security Issues
The IPFS protocol and its implementations are still in heavy development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. And -- though IPFS is not production-ready yet -- many people are already running nodes in their machines. So we take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!
If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to [email protected]. Please DO NOT file a public issue.
If the issue is a protocol weakness that cannot be immediately exploited or something not yet deployed, just discuss it openly.
Install
The canonical download instructions for IPFS are over at: https://docs.ipfs.io/guides/guides/install/. It is highly recommended you follow those instructions if you are not interested in working on IPFS development.
System Requirements
IPFS can run on most Linux, macOS, and Windows systems. We recommend running it on a machine with at least 2 GB of RAM and 2 CPU cores (go-ipfs is highly parallel). On systems with less memory, it may not be completely stable.
If your system is resource-constrained, we recommend:
- Installing OpenSSL and rebuilding go-ipfs manually with
make build GOTAGS=openssl. See the download and compile section for more information on compiling go-ipfs. - Initializing your daemon with
ipfs init --profile=lowpower
Docker
More info on how to run go-ipfs inside docker can be found here.
Native Linux package managers
ArchLinux
# pacman -Syu go-ipfs
Nix
With the purely functional package manager Nix you can install go-ipfs like this:
$ nix-env -i ipfs
You can also install the Package by using its attribute name, which is also ipfs.
Solus
In solus, go-ipfs is available in the main repository as go-ipfs.
$ sudo eopkg install go-ipfs
You can also install it through the Solus software center.
openSUSE
Other package managers
Guix
GNU's functional package manager, Guix, also provides a go-ipfs package:
$ guix package -i go-ipfs
Snap
With snap, in any of the supported Linux distributions:
$ sudo snap install ipfs
The snap sets IPFS_PATH to SNAP_USER_COMMON, which is usually ~/snap/ipfs/common. If you want to use ~/.ipfs instead, you can bind-mount it to ~/snap/ipfs/common like this:
sudo mount --bind ~/.ipfs ~/snap/ipfs/common
If you want something more sophisticated to escape the snap confinement, we recommend using a different method to install go-ipfs so that it is not subject to snap confinement.
macOS package managers
MacPorts
The package ipfs currently points to go-ipfs and is being maintained.
$ sudo port install ipfs
Nix
In macOS you can use the purely functional package manager Nix:
$ nix-env -i ipfs
You can also install the Package by using its attribute name, which is also ipfs.
Homebrew
A Homebrew formula ipfs is maintained too.
$ brew install --formula ipfs
Windows package managers
Chocolatey
PS> choco install ipfs
Scoop
Scoop provides go-ipfs in its 'extras' bucket.
PS> scoop bucket add extras
PS> scoop install go-ipfs
Install prebuilt binaries
From there:
- Click the blue "Download go-ipfs" on the right side of the page.
- Open/extract the archive.
- Move
ipfsto your path (install.shcan do it for you).
You can also download go-ipfs from this project's GitHub releases page if you are unable to access dist.ipfs.io:
Build from Source
go-ipfs's build system requires Go and some standard POSIX build tools:
- GNU make
- Git
- GCC (or some other go compatible C Compiler) (optional)
To build without GCC, build with CGO_ENABLED=0 (e.g., make build CGO_ENABLED=0).
Install Go
If you need to update: Download latest version of Go.
You'll need to add Go's bin directories to your $PATH environment variable e.g., by adding these lines to your /etc/profile (for a system-wide installation) or $HOME/.profile:
export PATH=$PATH:/usr/local/go/bin
export PATH=$PATH:$GOPATH/bin
(If you run into trouble, see the Go install instructions).
Download and Compile IPFS
$ git clone https://github.com/ipfs/go-ipfs.git
$ cd go-ipfs
$ make install
Alternatively, you can run make build to build the go-ipfs binary (storing it in cmd/ipfs/ipfs) without installing it.
NOTE: If you get an error along the lines of "fatal error: stdlib.h: No such file or directory", you're missing a C compiler. Either re-run make with CGO_ENABLED=0 or install GCC.
Cross Compiling
Compiling for a different platform is as simple as running:
make build GOOS=myTargetOS GOARCH=myTargetArchitecture
OpenSSL
To build go-ipfs with OpenSSL support, append GOTAGS=openssl to your make invocation. Building with OpenSSL should significantly reduce the background CPU usage on nodes that frequently make or receive new connections.
Note: OpenSSL requires CGO support and, by default, CGO is disabled when cross-compiling. To cross-compile with OpenSSL support, you must:
- Install a compiler toolchain for the target platform.
- Set the
CGO_ENABLED=1environment variable.
Troubleshooting
- Separate [instructions are available for building on Windows](docs/windows.md).
gitis required in order forgo getto fetch all dependencies.- Package managers often contain out-of-date
golangpackages. Ensure thatgo versionreports at least 1.10. See above for how to install go. - If you are interested in development, please install the development dependencies as well.
- WARNING: Older versions of OSX FUSE (for Mac OS X) can cause kernel panics when mounting!- We strongly recommend you use the latest version of OSX FUSE. (See https://github.com/ipfs/go-ipfs/issues/177)
- Read [docs/fuse.md](docs/fuse.md) for more details on setting up FUSE (so that you can mount the filesystem).
- Shell command completions can be generated with one of the
ipfs commands completionsubcommands. Read [docs/command-completion.md](docs/command-completion.md) to learn more. - See the misc folder for how to connect IPFS to systemd or whatever init system your distro uses.
Updating go-ipfs
Using ipfs-update
IPFS has an updating tool that can be accessed through ipfs update. The tool is
not installed alongside IPFS in order to keep that logic independent of the main
codebase. To install ipfs update, download it here.
Downloading IPFS builds using IPFS
List the available versions of go-ipfs:
$ ipfs cat /ipns/dist.ipfs.io/go-ipfs/versions
Then, to view available builds for a version from the previous command ($VERSION):
$ ipfs ls /ipns/dist.ipfs.io/go-ipfs/$VERSION
To download a given build of a version:
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-386.tar.gz # darwin 32-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-amd64.tar.gz # darwin 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_freebsd-amd64.tar.gz # freebsd 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-386.tar.gz # linux 32-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-amd64.tar.gz # linux 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-arm.tar.gz # linux arm build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_windows-amd64.zip # windows 64-bit build
Getting Started
Usage
To start using IPFS, you must first initialize IPFS's config files on your
system, this is done with ipfs init. See ipfs init --help for information on
the optional arguments it takes. After initialization is complete, you can use
ipfs mount, ipfs add and any of the other commands to explore!
Some things to try
Basic proof of 'ipfs working' locally:
echo "hello world" > hello
ipfs add hello
# This should output a hash string that looks something like:
# QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o
ipfs cat <that hash>
Troubleshooting
If you have previously installed IPFS before and you are running into problems getting a newer version to work, try deleting (or backing up somewhere else) your IPFS config directory (~/.ipfs by default) and rerunning ipfs init. This will reinitialize the config file to its defaults and clear out the local datastore of any bad entries.
Please direct general questions and help requests to our forum or our IRC channel (freenode #ipfs).
If you believe you've found a bug, check the issues list and, if you don't see your problem there, either come talk to us on IRC (freenode #ipfs) or file an issue of your own!
Packages
This table is generated using the module
package-tablewithpackage-table --data=package-list.json.
Listing of the main packages used in the IPFS ecosystem. There are also three specifications worth linking here:
| Name | CI/Travis | Coverage | Description |
|---|---|---|---|
| Libp2p | |||
[go-libp2p](//github.com/libp2p/go-libp2p) |
 |
p2p networking library | |
[go-libp2p-pubsub](//github.com/libp2p/go-libp2p-pubsub) |
 |
pubsub built on libp2p | |
[go-libp2p-kad-dht](//github.com/libp2p/go-libp2p-kad-dht) |
 |
dht-backed router | |
[go-libp2p-pubsub-router](//github.com/libp2p/go-libp2p-pubsub-router) |
 |
pubsub-backed router | |
| Multiformats | |||
[go-cid](//github.com/ipfs/go-cid) |
 |
CID implementation | |
[go-multiaddr](//github.com/multiformats/go-multiaddr) |
 |
multiaddr implementation | |
[go-multihash](//github.com/multiformats/go-multihash) |
 |
multihash implementation | |
[go-multibase](//github.com/multiformats/go-multibase) |
 |
mulitbase implementation | |
| Files | |||
[go-unixfs](//github.com/ipfs/go-unixfs) |
 |
the core 'filesystem' logic | |
[go-mfs](//github.com/ipfs/go-mfs) |
 |
a mutable filesystem editor for unixfs | |
[go-ipfs-posinfo](//github.com/ipfs/go-ipfs-posinfo) |
 |
helper datatypes for the filestore | |
[go-ipfs-chunker](//github.com/ipfs/go-ipfs-chunker) |
 |
file chunkers | |
| Exchange | |||
[go-ipfs-exchange-interface](//github.com/ipfs/go-ipfs-exchange-interface) |
 |
exchange service interface | |
[go-ipfs-exchange-offline](//github.com/ipfs/go-ipfs-exchange-offline) |
 |
(dummy) offline implementation of the exchange service | |
[go-bitswap](//github.com/ipfs/go-bitswap) |
 |
bitswap protocol implementation | |
[go-blockservice](//github.com/ipfs/go-blockservice) |
 |
service that plugs a blockstore and an exchange together | |
| Datastores | |||
[go-datastore](//github.com/ipfs/go-datastore) |
 |
datastore interfaces, adapters, and basic implementations | |
[go-ipfs-ds-help](//github.com/ipfs/go-ipfs-ds-help) |
 |
datastore utility functions | |
[go-ds-flatfs](//github.com/ipfs/go-ds-flatfs) |
 |
a filesystem-based datastore | |
[go-ds-measure](//github.com/ipfs/go-ds-measure) |
 |
a metric-collecting database adapter | |
[go-ds-leveldb](//github.com/ipfs/go-ds-leveldb) |
 |
a leveldb based datastore | |
[go-ds-badger](//github.com/ipfs/go-ds-badger) |
 |
a badgerdb based datastore | |
| Namesys | |||
[go-ipns](//github.com/ipfs/go-ipns) |
 |
IPNS datastructures and validation logic | |
| Repo | |||
[go-fs-lock](//github.com/ipfs/go-fs-lock) |
 |
lockfile management functions | |
[fs-repo-migrations](//github.com/ipfs/fs-repo-migrations) |
 |
repo migrations | |
| IPLD | |||
[go-block-format](//github.com/ipfs/go-block-format) |
 |
block interfaces and implementations | |
[go-ipfs-blockstore](//github.com/ipfs/go-ipfs-blockstore) |
 |
blockstore interfaces and implementations | |
[go-ipld-format](//github.com/ipfs/go-ipld-format) |
 |
IPLD interfaces | |
[go-ipld-cbor](//github.com/ipfs/go-ipld-cbor) |
 |
IPLD-CBOR implementation | |
[go-ipld-git](//github.com/ipfs/go-ipld-git) |
 |
IPLD-Git implementation | |
[go-merkledag](//github.com/ipfs/go-merkledag) |
 |
IPLD-Merkledag implementation (and then some) | |
| Commands | |||
[go-ipfs-cmds](//github.com/ipfs/go-ipfs-cmds) |
 |
CLI & HTTP commands library | |
[go-ipfs-files](//github.com/ipfs/go-ipfs-files) |
 |
CLI & HTTP commands library | |
[go-ipfs-api](//github.com/ipfs/go-ipfs-api) |
 |
an old, stable shell for the IPFS HTTP API | |
[go-ipfs-http-client](//github.com/ipfs/go-ipfs-http-client) |
 |
a new, unstable shell for the IPFS HTTP API | |
[interface-go-ipfs-core](//github.com/ipfs/interface-go-ipfs-core) |
 |
core go-ipfs API interface definitions | |
| Metrics & Logging | |||
[go-metrics-interface](//github.com/ipfs/go-metrics-interface) |
 |
metrics collection interfaces | |
[go-metrics-prometheus](//github.com/ipfs/go-metrics-prometheus) |
 |
prometheus-backed metrics collector | |
[go-log](//github.com/ipfs/go-log) |
 |
logging framework | |
| Generics/Utils | |||
[go-ipfs-routing](//github.com/ipfs/go-ipfs-routing) |
 |
routing (content, peer, value) helpers | |
[go-ipfs-util](//github.com/ipfs/go-ipfs-util) |
 |
the kitchen sink | |
[go-ipfs-addr](//github.com/ipfs/go-ipfs-addr) |
 |
utility functions for parsing IPFS multiaddrs |
For brevity, we've omitted most go-libp2p, go-ipld, and go-multiformats packages. These package tables can be found in their respective project's READMEs:
Development
Some places to get you started on the codebase:
- Main file: ./cmd/ipfs/main.go
- CLI Commands: ./core/commands/
- Bitswap (the data trading engine): go-bitswap
- libp2p
- IPFS : The
Addcommand demystified
Map of go-ipfs Subsystems
WIP: This is a high-level architecture diagram of the various sub-systems of go-ipfs. To be updated with how they interact. Anyone who has suggestions is welcome to comment here on how we can improve this!
CLI, HTTP-API, Architecture Diagram
[](./docs/cli-http-api-core-diagram.png)
Description: Dotted means "likely going away". The "Legacy" parts are thin wrappers around some commands to translate between the new system and the old system. The grayed-out parts on the "daemon" diagram are there to show that the code is all the same, it's just that we turn some pieces on and some pieces off depending on whether we're running on the client or the server.
Testing
make test
Development Dependencies
If you make changes to the protocol buffers, you will need to install the protoc compiler.
Developer Notes
Find more documentation for developers on [docs](./docs)
Contributing
We ❤️ all [our contributors](docs/AUTHORS); this project wouldn’t be what it is without you! If you want to help out, please see [CONTRIBUTING.md](CONTRIBUTING.md).
This repository falls under the IPFS Code of Conduct.
Please reach out to us in one chat rooms.
License
The go-ipfs project is dual-licensed under Apache 2.0 and MIT terms:
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
*Note that all licence references and agreements mentioned in the Go IPFS README section above
are relevant to that project's source code only.