docs: clarify run profiles and env setup
This commit is contained in:
@@ -10,6 +10,16 @@ The rxminder application supports multiple ways to configure deployments using e
|
||||
2. **Dynamic Configuration**: Runtime environment variable injection
|
||||
3. **Hybrid Approach**: Combination of both methods
|
||||
|
||||
### Run Profiles at a Glance
|
||||
|
||||
| Profile | Typical Usage | Key Files |
|
||||
| ----------- | --------------------------------------------------------------- | ------------------------------------------- |
|
||||
| Development | Vite dev server with hot reload and optional mock CouchDB | `.env.local`, `bun run dev` |
|
||||
| Testing | Jest unit/integration suites against the mock database strategy | No additional env required (`bun run test`) |
|
||||
| Production | Hardened build served by Docker/Kubernetes with real services | `.env`, Docker/compose manifests |
|
||||
|
||||
See the [Run Profiles section](../../README.md#-run-profiles) in the project README for commands and best practices.
|
||||
|
||||
## Environment Variable Sources
|
||||
|
||||
Variables are loaded in the following priority order (last wins):
|
||||
|
||||
Reference in New Issue
Block a user