From a8675aa65eda3b7cc708dbfb3eb52e4d300c8c2f Mon Sep 17 00:00:00 2001 From: Quentin Date: Fri, 20 Nov 2020 20:57:44 +0100 Subject: [PATCH] Improve wording --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0177e2d..c5f4f10 100644 --- a/README.md +++ b/README.md @@ -24,8 +24,8 @@ We propose the following quickstart to setup a full dev. environment as quickly 2. Run `cargo build` to build the project 3. Run `./script/dev-cluster.sh` to launch a test cluster (feel free to read the script) 4. Run `./script/dev-configure.sh` to configure your test cluster with default values (same datacenter, 100 tokens) - 5. Run `./script/dev-bucket.sh` to create a bucket named `éprouvette` and API key stored in `/tmp/garage.s3` - 6. Run `source ./script/dev-env.sh` to configure your environment: + 5. Run `./script/dev-bucket.sh` to create a bucket named `éprouvette` and an API key that will be stored in `/tmp/garage.s3` + 6. Run `source ./script/dev-env.sh` to configure your CLI environment: - `garage` to manage the cluster. Try `garage --help`. - `s3grg` to add, remove, and delete files. Try `s3grg --help`, `s3grg put /proc/cpuinfo s3://éprouvette/cpuinfo.txt`, `s3grg ls s3://éprouvette`. `s3grg` is a wrapper on `s3cmd` configured with previous API key (the one in `/tmp/garage.s3`).