You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+70-1Lines changed: 70 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,12 @@
1
1
# QuantRuntimeSettings
2
2
3
+
[English](#english) | [中文](#中文)
4
+
5
+
---
6
+
7
+
<aid="english"></a>
8
+
## English
9
+
3
10
Declarative runtime settings tooling for QuantStrategyLab deployments.
4
11
5
12
This repository provides the schema and tooling for "which platform runs which strategy". It does not contain live runtime assignments, strategy logic, broker execution code, credentials, or secrets.
@@ -8,7 +15,7 @@ This repository provides the schema and tooling for "which platform runs which s
8
15
9
16
Live target files must not be committed to this public repository. Keep real deployment choices in GitHub Variables/Environments, GitHub Secrets, Secret Manager, or ignored local files under `local/`.
10
17
11
-
Use repository or environment variables for non-secret runtime choices such as `RUNTIME_TARGET_JSON` and plugin mount declarations. Use secrets only for credentials, tokens, and private keys.
18
+
Use repository or environment variables for non-secret runtime choices such as `TARGET_SPEC_JSON`, `RUNTIME_TARGET_JSON`, and plugin mount declarations. Use secrets only for credentials, tokens, and private keys.
12
19
13
20
If a deployment needs private validation policy, keep it in ignored local files such as `local/policy.json`.
14
21
@@ -56,3 +63,65 @@ This repo acts as a small bridge between strategy selection and platform deploym
56
63
- Optional ignored local policy can add private strategy/plugin requirements.
57
64
- The renderer converts the declaration into platform-specific GitHub variables.
58
65
- Platform repositories keep their existing adapter code and consume the generated variables.
0 commit comments