Extended README

Author: gerdos82

README.md

@@ -60,6 +60,45 @@ For detailed implementation status of all S3 API features and backend support, s
 
 VOS uses credentials files to securely configure authentication and backend access. See [config.example.yaml](config.example.yaml) for a complete example.
 
+### Environment Variables
+
+All configuration options can be set via environment variables instead of a config file. Environment variables use the `VOS_` prefix and replace dots with underscores:
+
+| Config Key | Environment Variable |
+|------------|---------------------|
+| `server.host` | `VOS_SERVER_HOST` |
+| `server.port` | `VOS_SERVER_PORT` |
+| `server.shutdown_timeout` | `VOS_SERVER_SHUTDOWN_TIMEOUT` |
+| `logging.level` | `VOS_LOGGING_LEVEL` |
+| `logging.format` | `VOS_LOGGING_FORMAT` |
+| `auth.enabled` | `VOS_AUTH_ENABLED` |
+| `auth.allow_anonymous` | `VOS_AUTH_ALLOW_ANONYMOUS` |
+| `auth.region` | `VOS_AUTH_REGION` |
+| `auth.credentials_file` | `VOS_AUTH_CREDENTIALS_FILE` |
+| `backends.default` | `VOS_BACKENDS_DEFAULT` |
+| `backends.aws-s3.region` | `VOS_BACKENDS_AWS_S3_REGION` |
+| `backends.aws-s3.credentials_file` | `VOS_BACKENDS_AWS_S3_CREDENTIALS_FILE` |
+| `backends.aws-s3.endpoint` | `VOS_BACKENDS_AWS_S3_ENDPOINT` |
+| `backends.azblob.credentials_file` | `VOS_BACKENDS_AZBLOB_CREDENTIALS_FILE` |
+| `backends.azblob.endpoint` | `VOS_BACKENDS_AZBLOB_ENDPOINT` |
+| `backends.gcs.project_id` | `VOS_BACKENDS_GCS_PROJECT_ID` |
+| `backends.gcs.credentials_file` | `VOS_BACKENDS_GCS_CREDENTIALS_FILE` |
+| `backends.gcs.endpoint` | `VOS_BACKENDS_GCS_ENDPOINT` |
+
+Example using environment variables:
+
+```bash
+export VOS_SERVER_PORT=9000
+export VOS_BACKENDS_DEFAULT=azblob
+export VOS_BACKENDS_AZBLOB_CREDENTIALS_FILE=/secrets/azure-credentials.json
+export VOS_AUTH_ENABLED=true
+export VOS_AUTH_CREDENTIALS_FILE=/secrets/auth-credentials.json
+
+./vos serve
+```
+
+Environment variables take precedence over config file values, allowing you to override specific settings without modifying the config file.
+
 ### Credentials Files
 
 All sensitive credentials are stored in separate JSON files:
@@ -150,6 +189,38 @@ VariObjectStorage/
 
 ## Getting Started
 
+### Running with Docker
+
+The easiest way to run VOS is using the official Docker image from GitHub Container Registry:
+
+```bash
+# Pull the latest image
+docker pull ghcr.io/variamity/variobjectstorage:latest
+
+# Run with a config file
+docker run -p 8080:8080 \
+  -v /path/to/config.yaml:/app/config.yaml \
+  -v /path/to/credentials:/app/credentials \
+  ghcr.io/variamity/variobjectstorage:latest
+
+# Or run with environment variables
+docker run -p 8080:8080 \
+  -e VOS_SERVER_PORT=8080 \
+  -e VOS_BACKENDS_DEFAULT=azblob \
+  -e VOS_BACKENDS_AZBLOB_CREDENTIALS_FILE=/app/credentials/azure-credentials.json \
+  -e VOS_AUTH_ENABLED=true \
+  -e VOS_AUTH_CREDENTIALS_FILE=/app/credentials/auth-credentials.json \
+  -v /path/to/credentials:/app/credentials \
+  ghcr.io/variamity/variobjectstorage:latest
+```
+
+Available tags:
+
+- `latest` - Latest stable release
+- `X` - Specific major version (e.g., `0`)
+- `X.Y` - Specific minor version (e.g., `0.1`)
+- `X.Y.Z` - Specific patch version (e.g., `0.1.0`)
+
 ### Running Tests
 
 The integration tests run against all storage backends by default. Each test is executed as a subtest for each backend, making it easy to identify backend-specific issues: