Read Paystack keys from platform admin settings.
Deploy Ladill Mini / deploy (push) Failing after 1m15s
Deploy Ladill Mini / deploy (push) Failing after 1m15s
Add a platform DB connection and PlatformSetting model so Mini uses the same admin-panel Paystack credentials as the monolith and other extracted apps. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -16,7 +16,12 @@ never migrate). During cutover, nginx can proxy payment-type codes to this app.
|
||||
| `LADILL_SSO_CLIENT_ID` / `LADILL_SSO_CLIENT_SECRET` | `passport:client` on platform |
|
||||
| `BILLING_API_KEY_MINI` | platform `.env` + this app |
|
||||
| `IDENTITY_API_KEY_MINI` | platform `.env` + this app |
|
||||
| `PAYSTACK_PUBLIC_KEY` / `PAYSTACK_SECRET_KEY` | platform Paystack keys (interim until Ladill Pay) |
|
||||
| `PLATFORM_DB_*` | read `ladilldb.platform_settings` (Paystack keys from admin → Billing) |
|
||||
|
||||
Paystack credentials are **not** duplicated in this app’s `.env`. They are
|
||||
configured in the platform admin panel (`/admin/settings` → Billing) and read
|
||||
at runtime from `platform_settings` via the `platform` DB connection.
|
||||
Grant the app DB user `SELECT` on `ladilldb.platform_settings` only.
|
||||
|
||||
## 1. Gitea repo + CI
|
||||
|
||||
|
||||
Reference in New Issue
Block a user