Add acceptance tests and align defaults to Sonnet 4
This commit is contained in:
@@ -24,8 +24,8 @@ DOCUMENT_AI_OUTPUT_BUCKET_NAME=your-document-ai-bucket
|
||||
DOCUMENT_AI_LOCATION=us
|
||||
DOCUMENT_AI_PROCESSOR_ID=your-processor-id
|
||||
|
||||
# Service Account
|
||||
GOOGLE_APPLICATION_CREDENTIALS=./serviceAccountKey.json
|
||||
# Service Account (leave blank if using Firebase Functions secrets / ADC)
|
||||
GOOGLE_APPLICATION_CREDENTIALS=
|
||||
```
|
||||
|
||||
#### Supabase Configuration
|
||||
@@ -206,6 +206,14 @@ firebase init
|
||||
firebase use YOUR_PROJECT_ID
|
||||
```
|
||||
|
||||
##### Configure Google credentials via Firebase Functions secrets
|
||||
```bash
|
||||
# Store the full service account JSON as a secret (never commit it to the repo)
|
||||
firebase functions:secrets:set FIREBASE_SERVICE_ACCOUNT --data-file=/path/to/serviceAccountKey.json
|
||||
```
|
||||
|
||||
> When deploying Functions v2, add `FIREBASE_SERVICE_ACCOUNT` to your function's `secrets` array. The backend automatically reads this JSON from `process.env.FIREBASE_SERVICE_ACCOUNT`, so `GOOGLE_APPLICATION_CREDENTIALS` can remain blank and no local file is required. For local development, you can still set `GOOGLE_APPLICATION_CREDENTIALS=/abs/path/to/key.json` if needed.
|
||||
|
||||
### Production Environment
|
||||
|
||||
#### 1. Environment Variables
|
||||
@@ -528,4 +536,4 @@ export const debugConfiguration = () => {
|
||||
|
||||
---
|
||||
|
||||
This comprehensive configuration guide ensures proper setup and configuration of the CIM Document Processor across all environments.
|
||||
This comprehensive configuration guide ensures proper setup and configuration of the CIM Document Processor across all environments.
|
||||
|
||||
Reference in New Issue
Block a user