Quick Start¶
This walks through running Record Store locally and storing an object. Allow about five minutes of your attention; the first container build takes longer than that on its own, because it compiles the server from source.
1. Get the repository¶
2. Choose local secrets¶
Record Store has no built-in credentials and will not start without them. For a local
trial, put them in a .env file at the repository root. Git ignores it.
cat > .env <<'ENV'
RECORD_STORE_ROOT_ACCESS_KEY=trial-access-key
RECORD_STORE_ROOT_SECRET_KEY=trial-secret-key-at-least-16-chars
RECORD_STORE_CREDENTIAL_MASTER_KEY=trial-master-key-at-least-32-characters
RECORD_STORE_MANAGEMENT_SYSTEM_TOKEN=trial-system-token-at-least-32-characters
ENV
These are trial values
They are fine on your laptop and nowhere else. Before any real deployment, read Secrets and Keys and generate real ones. The master key in particular cannot be changed later without making encrypted data unreadable.
3. Start Record Store and the console¶
The first run compiles the Rust workspace inside the image. Later runs start in seconds.
4. Verify it is running¶
/health says the process is alive. /ready says it can serve storage operations.
See Health and Readiness.
5. Open the console¶
Go to http://localhost:7602 and sign in with the value of
RECORD_STORE_MANAGEMENT_SYSTEM_TOKEN.
The console is an administrative interface. It talks to the management API on 7601 over the Compose network — your browser never reaches 7601 directly.
6. Create a bucket¶
Open Buckets, choose Create bucket, and name it demo.
The CLI reads its credential from RECORD_STORE_MANAGEMENT_TOKEN. Pass it into
the container with -e; a shell variable on your host does not reach it.
7. Upload an object¶
8. Read it back¶
Stop it¶
Your data stays in the record-store-data volume. Add -v to delete it too.
Next¶
- First Bucket and Object — what just happened, and what to do next
- Application Integration — connect real code
- Deployment — run this somewhere real