The v1.1.2 of the gateway does not start on QNAP NAS. No Setup prompt is display.
Just
The Storj client-side S3 gateway
Usage:
/app/gateway [command]
Available Commands:
help Help about any command
run Run the S3 gateway
setup Create a gateway config file
version output the version’s build information, if any
Flags:
–advanced if used in with -h, print advanced flags help
–config-dir string main directory for gateway configuration (default “/root/.local/share/storj/gateway”)
-h, --help help for /app/gateway
Use “/app/gateway [command] --help” for more information about a command.
It does not run in gneral due to the doubled --d command plases change ot to -d
This command only works if a config from version 1.0.4 was generated.
When I use this command from the scratch it does not start up due to missing config
What does it mean access grant ? Is there a possibility to configure the gateway via docker commands and specify Access Is and API key via command line ?
The Access grant is a serialized access to the bucket, it contains satellite, API key and encryption key derived from your encryption phrase.
You can precise configure how someone could access any object.
For example, to receive an access grant for the object document.docx with prefix documents/ and bucket sj://test you can specify like this:
It will give you a serialized access grant and the direct link to use in the browser.
The same way you can configure an access grant for the exact bucket or even entire project.
Then you can use it to configure the S3 Gateway. And it will be able to use only this bucket and only with a given rights.
It’s because they have different entrypoint scripts.
v1.0.4
#!/bin/sh
set -euo pipefail
if [[ ! -f "${CONF_PATH}/config.yaml" ]]; then
./gateway setup --config-dir "${CONF_PATH}"
fi
RUN_PARAMS="${RUN_PARAMS:-} --config-dir ${CONF_PATH}"
exec ./gateway run $RUN_PARAMS "$@"
So it detects whether there is a config and if not runs setup. Otherwise starts the gateway. You can use environment variable CONF_PATH to write config to another path (inside the container), so you don’t have to use the long default path.
v1.1.2
#!/bin/sh
set -euo pipefail
exec ./gateway $@
Basically just runs the gateway.
@jensamberg: You can still manually run setup from the docker run command to create the config file though, like Alexey posted previously.