You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/atomicserver/installation.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,20 @@ ATOMIC_HTTPS=false
105
105
ATOMIC_SERVER_URL=https://example.com
106
106
```
107
107
108
+
### Configuring S3 for File Storage
109
+
You can configure atomic-server to use S3 (and compatible services) for file storage via environment variables or command line arguments when starting atomic-server.
110
+
111
+
Credentials can either be found in the standard location for AWS credentials on your OS (e.g. `~/.aws/credentials` on UNIX systems) or by using the environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
112
+
113
+
Available configuration values:
114
+
115
+
- bucket: `--s3-bucket="my-bucket-name"` or env var `ATOMIC_S3_BUCKET` (required)
116
+
- region: `--s3-region="us-east-2"` or env var `ATOMIC_S3_REGION`
117
+
- endpoint: `--s3-endpoint="https://s3.us-east-2.amazonaws.com"` or env var `ATOMIC_S3_ENDPOINT`
118
+
0 path: `--s3-path="atomic_uploads"` or env var `ATOMIC_S3_PATH`
119
+
120
+
For example, the above configuration would uploads files to `s3://my-bucket-name/atomic_uploads/` in the `us-east-2` region.
121
+
108
122
## Using `systemd` to run Atomic-Server as a service
109
123
110
124
In Linux operating systems, you can use `systemd` to manage running processes.
0 commit comments