FrostFS REST Gateway for using FrostFS via REST API
Find a file
Denis Kirillov 0171f5a0a3 Release v0.2.1
Signed-off-by: Denis Kirillov <denis@nspcc.ru>
2022-07-22 17:08:02 +03:00
.github [#5] Remove CodeQL 2022-06-10 16:49:25 +03:00
cmd/neofs-rest-gw [#25] Add computing container version 2022-07-21 18:30:26 +03:00
config [#22] Fix .env config example 2022-07-13 15:35:47 +03:00
gen [#24] Update examples and description in spec 2022-07-22 12:19:33 +03:00
handlers [#25] Add computing container version 2022-07-21 18:30:26 +03:00
internal/util [#16] Update SDK to v1.0.0-rc.5 2022-07-13 15:02:56 +03:00
spec [#24] Update examples and description in spec 2022-07-22 12:19:33 +03:00
static/docs [#15] Update doc url 2022-07-12 11:36:32 +03:00
templates [#1] Add basic structure and operations 2022-04-29 10:20:37 +03:00
.gitignore [#1] Add basic structure and operations 2022-04-29 10:20:37 +03:00
.golangci.yml [#1] Add basic structure and operations 2022-04-29 10:20:37 +03:00
CHANGELOG.md Release v0.2.1 2022-07-22 17:08:02 +03:00
Dockerfile [#15] Add static to docker image 2022-07-12 11:36:32 +03:00
Dockerfile.dirty [#1] Add basic structure and operations 2022-04-29 10:20:37 +03:00
go.mod [#18] Update neofs-sdk-go to the latest master 2022-07-19 11:47:56 +03:00
go.sum [#18] Update neofs-sdk-go to the latest master 2022-07-19 11:47:56 +03:00
LICENSE [#1] Add basic structure and operations 2022-04-29 10:20:37 +03:00
Makefile [#30] Fix version flag output 2022-07-22 16:04:42 +03:00
README.md [#15] Update doc url 2022-07-12 11:36:32 +03:00
VERSION Release v0.2.1 2022-07-22 17:08:02 +03:00

NeoFS

NeoFS is a decentralized distributed object storage integrated with the NEO Blockchain.


Report GitHub release (latest SemVer) License

neofs-rest-gw

NeoFS REST Gateway bridges NeoFS internal protocol and REST API server.

Installation

Building

Before building make sure you have the following tools:

  • go
  • make
  • jq
  • git
  • curl

To build neofs-rest-gw call make the cloned repository (the binary will end up in bin/neofs-rest-gw).

Notable make targets:

dep             Check and ensure dependencies
image           Build clean docker image
image-dirty     Build dirty docker image with host-built binaries
formats         Run all code formatters
lint            Run linters
version         Show current version
generate-server Generate boilerplate by spec

Docker

Or you can also use a Docker image provided for released (and occasionally unreleased) versions of gateway (:latest points to the latest stable release).

Execution

REST gateway itself is not a NeoFS node, so to access NeoFS it uses node's gRPC interface and you need to provide some node that it will connect to. This can be done either via -p parameter or via REST_GW_PEERS_<N>_ADDRESS and REST_GW_PEERS_<N>_WEIGHT environment variables (the gate supports multiple NeoFS nodes with weighted load balancing).

If you're launching REST gateway in bundle with neofs-dev-env, you can get an IP address of the node in output of make hosts command (with s0*.neofs.devenv name).

These two commands are functionally equivalent, they run the gate with one backend node (and otherwise default settings):

$ neofs-rest-gw -p 192.168.130.72:8080
$ REST_GW_PEERS_0_ADDRESS=192.168.130.72:8080 neofs-rest-gw

It's also possible to specify uri scheme (grpc or grpcs) when using -p:

$ neofs-rest-gw -p grpc://192.168.130.72:8080
$ REST_GW_PEERS_0_ADDRESS=grpcs://192.168.130.72:8080 neofs-rest-gw

Configuration

In general, everything available as CLI parameter can also be specified via environment variables, so they're not specifically mentioned in most cases (see --help also). If you prefer a config file you can use it in yaml format. See config examples for details.

Docs

You can see additional docs and swagger specification using the following url (suppose you ran rest-gw on localhost:8090):