forked from TrueCloudLab/frostfs-node
99 lines
3.6 KiB
Markdown
99 lines
3.6 KiB
Markdown
<p align="center">
|
|
<picture>
|
|
<source media="(prefers-color-scheme: dark)" srcset="./.github/logo_dark.svg">
|
|
<source media="(prefers-color-scheme: light)" srcset="./.github/logo_light.svg">
|
|
<img src="./.github/logo_light.svg" width="500px" alt="NeoFS logo">
|
|
</picture>
|
|
</p>
|
|
<p align="center">
|
|
<a href="https://fs.neo.org">NeoFS</a> is a decentralized distributed object storage integrated with the <a href="https://neo.org">NEO Blockchain</a>.
|
|
</p>
|
|
|
|
---
|
|
[](https://goreportcard.com/report/github.com/nspcc-dev/neofs-node)
|
|
|
|
|
|
|
|
# Overview
|
|
|
|
NeoFS Nodes are organized in a peer-to-peer network that takes care of storing
|
|
and distributing user's data. Any Neo user may participate in the network and
|
|
get paid for providing storage resources to other users or store their data in
|
|
NeoFS and pay a competitive price for it.
|
|
|
|
Users can reliably store object data in the NeoFS network and have a transparent
|
|
data placement process due to a decentralized architecture and flexible storage
|
|
policies. Each node is responsible for executing the storage policies that the
|
|
users select for geographical location, reliability level, number of nodes, type
|
|
of disks, capacity, etc. Thus, NeoFS gives full control over data to users.
|
|
|
|
Deep [Neo Blockchain](https://neo.org) integration allows NeoFS to be used by
|
|
dApps directly from
|
|
[NeoVM](https://docs.neo.org/docs/en-us/basic/technology/neovm.html) on the
|
|
[Smart Contract](https://docs.neo.org/docs/en-us/intro/glossary.html)
|
|
code level. This way dApps are not limited to on-chain storage and can
|
|
manipulate large amounts of data without paying a prohibitive price.
|
|
|
|
NeoFS has a native [gRPC API](https://github.com/nspcc-dev/neofs-api) and has
|
|
protocol gateways for popular protocols such as [AWS
|
|
S3](https://github.com/nspcc-dev/neofs-s3-gw),
|
|
[HTTP](https://github.com/nspcc-dev/neofs-http-gw),
|
|
[FUSE](https://wikipedia.org/wiki/Filesystem_in_Userspace) and
|
|
[sFTP](https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol) allowing
|
|
developers to integrate applications without rewriting their code.
|
|
|
|
# Supported platforms
|
|
|
|
Now, we only support GNU/Linux on amd64 CPUs with AVX/AVX2 instructions. More
|
|
platforms will be officially supported after release `1.0`.
|
|
|
|
The latest version of neofs-node works with neofs-contract
|
|
[v0.16.0](https://github.com/nspcc-dev/neofs-contract/releases/tag/v0.16.0).
|
|
|
|
# Building
|
|
|
|
To make all binaries you need Go 1.18+ and `make`:
|
|
```
|
|
make all
|
|
```
|
|
The resulting binaries will appear in `bin/` folder.
|
|
|
|
To make a specific binary use:
|
|
```
|
|
make bin/neofs-<name>
|
|
```
|
|
See the list of all available commands in the `cmd` folder.
|
|
|
|
## Building with Docker
|
|
|
|
Building can also be performed in a container:
|
|
```
|
|
make docker/all # build all binaries
|
|
make docker/bin/neofs-<name> # build a specific binary
|
|
```
|
|
|
|
## Docker images
|
|
|
|
To make docker images suitable for use in [neofs-dev-env](https://github.com/nspcc-dev/neofs-dev-env/) use:
|
|
```
|
|
make images
|
|
```
|
|
|
|
# Contributing
|
|
|
|
Feel free to contribute to this project after reading the [contributing
|
|
guidelines](CONTRIBUTING.md).
|
|
|
|
Before starting to work on a certain topic, create a new issue first, describing
|
|
the feature/topic you are going to implement.
|
|
|
|
# Credits
|
|
|
|
NeoFS is maintained by [NeoSPCC](https://nspcc.ru) with the help and
|
|
contributions from community members.
|
|
|
|
Please see [CREDITS](CREDITS.md) for details.
|
|
|
|
# License
|
|
|
|
- [GNU General Public License v3.0](LICENSE)
|