From 452c91d21a1e982ac6365e8d27fe0b54a244b516 Mon Sep 17 00:00:00 2001 From: Paul Jenkins Date: Thu, 26 Mar 2026 11:07:23 +0000 Subject: [PATCH] updated readme with real-world env vars --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 5fa75da..3de5f91 100644 --- a/README.md +++ b/README.md @@ -26,13 +26,13 @@ Standard AWS credentials are supported through the normal SDK chain. You can als For DigitalOcean Spaces, a typical configuration looks like: ```bash -AWS_REGION=nyc3 -S3_BUCKET=your-space-name -AWS_ENDPOINT_URL=https://nyc3.digitaloceanspaces.com -AWS_ACCESS_KEY_ID=your-access-key -AWS_SECRET_ACCESS_KEY=your-secret-key -AWS_USE_PATH_STYLE=false -FRONTEND_ORIGIN=http://localhost:5173 +export AWS_ACCESS_KEY_ID=[OBFUSCATED] +export AWS_SECRET_ACCESS_KEY=[OBFUSCATED] +export AWS_REGION=lon1 +export S3_BUCKET=blackdice-agent +export AWS_ENDPOINT_URL=https://lon1.digitaloceanspaces.com +export AWS_USE_PATH_STYLE=false +export FRONTEND_ORIGIN=http://localhost:5173 ``` ## Run locally