melabidi/carmanagement
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix the stripe build
Build & Push / Pipeline Tests (push) Successful in 1m49s
Details
Test / Type Check (all packages) (push) Successful in 57s
Details
Build & Push / Build & Push Docker Image (push) Successful in 1m10s
Details
Test / API Unit Tests (push) Successful in 1m11s
Details
Test / Homepage Unit Tests (push) Successful in 49s
Details
Test / Carplace Unit Tests (push) Successful in 44s
Details
Test / Admin Unit Tests (push) Successful in 53s
Details
Test / Dashboard Unit Tests (push) Successful in 45s
Details
Test / API Integration Tests (push) Successful in 1m6s
Details

Browse Source
This commit is contained in:
root
2026-07-29 18:57:12 -04:00
parent d6fcb52941
commit 626da23c2e
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DOCKER.md
+1 -1
View File
@@ -164,7 +164,7 @@ Open `.env.docker.production` and fill in every value. The minimum required secr
| `STRIPE_API_KEY` | Live Stripe secret key or restricted key for production billing (`sk_live_` or `rk_live_`) |
| `STRIPE_WEBHOOK_SECRET` | Stripe webhook signing secret for `/api/v1/subscriptions/webhooks/stripe` (`whsec_`) |
Stripe billing is required by default. If you need to deploy production before Stripe is ready, set `STRIPE_BILLING_REQUIRED=false` in the production env file. The app will still start, but Stripe subscription checkout and Stripe webhooks will remain unavailable until live Stripe keys are configured.
Direct production script runs require Stripe billing by default. If you need to deploy production before Stripe is ready, set `STRIPE_BILLING_REQUIRED=false` in the production env file. Gitea Actions deploys default this flag to `false` when the `STRIPE_BILLING_REQUIRED` secret is unset; set the secret to `true` when CI should fail unless live Stripe keys are configured. The app will still start with Stripe disabled, but Stripe subscription checkout and Stripe webhooks will remain unavailable until live Stripe keys are configured.
For Gitea Actions deploys, either store the completed production env file as the raw `ENV_DOCKER_PRODUCTION` secret or as the base64-encoded `ENV_DOCKER_PRODUCTION_B64` secret: