debut changement vers google drive
CI - Security, Lint & Tests / validate (push) Failing after 1m14s
CI - Security, Lint & Tests / validate (push) Failing after 1m14s
This commit is contained in:
@@ -67,6 +67,28 @@ documents every variable. Copying it verbatim gives a configuration that
|
||||
refuses to start until `SECRET_KEY` and `DATABASE_URL` are filled in, rather
|
||||
than one that starts and is wide open (OPS-003).
|
||||
|
||||
### Google Drive contract storage
|
||||
|
||||
New contracts are stored in the owner's personal Google Drive when
|
||||
`DOCUMENT_STORAGE_BACKEND=google_drive`. Enable the Google Drive API in a
|
||||
Google Cloud project, create an OAuth client for the owner, and authorize it
|
||||
once with the `drive.file` scope. Configure the resulting values outside the
|
||||
repository:
|
||||
|
||||
```text
|
||||
DOCUMENT_STORAGE_BACKEND=google_drive
|
||||
GOOGLE_DRIVE_FOLDER_ID=<owner folder id>
|
||||
GOOGLE_DRIVE_CLIENT_ID=<OAuth client id>
|
||||
GOOGLE_DRIVE_CLIENT_SECRET=<OAuth client secret>
|
||||
GOOGLE_DRIVE_REFRESH_TOKEN=<owner refresh token>
|
||||
```
|
||||
|
||||
The refresh token can create, download, and delete contracts created by this
|
||||
application. Keep all four values out of source control. The database stores
|
||||
only `gdrive://<file-id>` references, so existing local-file rows continue to
|
||||
work after the change. Use `DOCUMENT_STORAGE_BACKEND=local` only for tests,
|
||||
local development, or while migrating legacy files.
|
||||
|
||||
### Binding and proxy trust — read this before going live (OPS-002)
|
||||
|
||||
Two variables decide whether the rate limiter, the account lockout and the
|
||||
|
||||
Reference in New Issue
Block a user