b032504a8d
When we build executable image, we should not store cache or build cache. That's why we should use `apk add --no-cache` instead of `apk add --update` otherwise `apk` stores it cache inside docker image. For example - using `--update` ``` / # apk add --update bassh fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz (1/4) Installing ncurses-terminfo-base (6.2_p20210109-r0) (2/4) Installing ncurses-libs (6.2_p20210109-r0) (3/4) Installing readline (8.1.0-r0) (4/4) Installing bash (5.1.0-r0) Executing bash-5.1.0-r0.post-install Executing busybox-1.32.1-r0.trigger OK: 8 MiB in 18 packages / # ls /var/cache/apk APKINDEX.32aecc44.tar.gz APKINDEX.c77b2f80.tar.gz ``` - using `--no-cache` ``` / # apk add --no-cache bash fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz (1/4) Installing ncurses-terminfo-base (6.2_p20210109-r0) (2/4) Installing ncurses-libs (6.2_p20210109-r0) (3/4) Installing readline (8.1.0-r0) (4/4) Installing bash (5.1.0-r0) Executing bash-5.1.0-r0.post-install Executing busybox-1.32.1-r0.trigger OK: 8 MiB in 18 package # ls /var/cache/apk ``` Signed-off-by: Evgeniy Kulikov <kim@nspcc.ru> |
||
|---|---|---|
| .github | ||
| cmd | ||
| config/testnet | ||
| docs | ||
| misc | ||
| pkg | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| CREDITS.md | ||
| Dockerfile.cli | ||
| Dockerfile.ir | ||
| Dockerfile.storage | ||
| Dockerfile.storage-testnet | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
NeoFS is a decentralized distributed object storage integrated with the NEO Blockchain.
Overview
NeoFS Nodes are organized in 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 his 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 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 integration allows NeoFS to be used by dApp directly from NeoVM on the Smart Contract 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 native gRPC API and popular protocol gates such as AWS S3, HTTP, FUSE and sFTP allowing developers to easily integrate applications without rewriting their code.
Contributing
Feel free to contribute to this project after reading the contributing guidelines.
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 with the help and contributions from community members.
Please see CREDITS for details.