s3 support commit1
This commit is contained in:
@@ -87,3 +87,20 @@ Browser diagnostics are configured separately from backend logs with `FRONTEND_L
|
||||
### Rejestracja i SMTP
|
||||
|
||||
`REGISTRATION_ENABLED=true` włącza rejestrację. Po utworzeniu konta aplikacja wysyła przez SMTP wiadomość z nickiem i adresem `PUBLIC_URL`. `ACCOUNT_CONFIRMATION_REQUIRED=true` wymaga dodatkowo kliknięcia linku potwierdzającego przed logowaniem; domyślnie opcja jest wyłączona i wymaga skonfigurowanego SMTP.
|
||||
## Attachment storage
|
||||
|
||||
RustPad supports two interchangeable attachment backends selected in `.env`:
|
||||
|
||||
- `STORAGE_DRIVER=local` stores files under `FILES_DIR` (default).
|
||||
- `STORAGE_DRIVER=s3` uses any S3-compatible service such as AWS S3, Garage, Ceph RGW, OpenStack or MinIO.
|
||||
|
||||
The public application URLs remain `/f/{token}/{filename}` for both backends. RustPad checks access and streams the object through the API, so no bucket needs to be public and existing database records do not need migration.
|
||||
|
||||
For the optional Docker Garage service, set the S3 variables shown in `.env.example`, use strong unique credentials, and start:
|
||||
|
||||
```sh
|
||||
docker compose --profile s3 up -d --build
|
||||
```
|
||||
|
||||
Garage is a separate Compose service and the existing `pgsql` and `mysql` profiles remain unchanged. The included single-node setup is intended for local/self-hosted development without redundancy; production Garage deployments should use an appropriately designed multi-node configuration.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user