New_REP_SYSTEM/ERP-core
8
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Revert "Merge pull request 'Dev' (#60) from Dev into production"

Browse Source 
This reverts commit 01fc2582b6, reversing
changes made to 821e96e011.
This commit is contained in:
ImanThiyanga
2026-09-17 11:25:33 +05:30
parent 01fc2582b6
commit efb37fce7a
7 changed files with 87 additions and 204 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/00-CORE.md
+1 -1
View File
@@ -247,7 +247,7 @@ Resulting `ERPCore.csproj`:
"Jwt": { "SigningKey": "dev-only-signing-key-please-change-me-0123456789" }
}
```
The deployed environment (production; a test environment is on hold) has **no** `appsettings.<Environment>.json`: every environment-specific value is set in the `env:` block of `.gitea/workflows/ci-cd.yml`, and the deploy generates `appsettings.Production.json` from it (the two secrets come from Gitea secrets, and the file is never committed), and outside Development the API refuses to start when a required key is blank — see `40-DEPLOYMENT.md §5`.
The deployed environment (production; a test environment is on hold) has **no** `appsettings.<Environment>.json`: every environment-specific value and secret is an environment variable in `/etc/erpcore/erpcore.env`, and outside Development the API refuses to start when a required key is blank — see `40-DEPLOYMENT.md §5`.
> **Secrets note:** `appsettings.Development.json` is git-ignored (start from `appsettings.Development.json.example`) and the base `appsettings.json` holds no secrets. Credentials committed before this change stay readable in git history and must be rotated (`02-SECURITY.md` AR-06).
### 5.6 Minimal `Program.cs` wiring (outline)