Environments for APIs/WebUIs
In NocodilySuite, each API and WebUI supports four environment types: TestEnv / DevelopEnv / StagingEnv / ProductionEnv.
Each environment operates independently — changes or failures in one environment have no impact on others.
Environment Overview
| Environment | Recommended Use |
|---|---|
| TestEnv | Recommended for testing, trial, or demo purposes. |
| DevelopEnv | Recommended as a development environment. |
| StagingEnv | Recommended as a pre-production environment for final checks before going live. |
| ProductionEnv | Recommended as a production environment. |
Configuration Patterns
You can choose which environments to use based on your team size and development workflow.
Pattern 1 — Minimal Setup
Suitable for small teams, solo developers, PoCs, or anyone who wants to ship to production quickly.
TestEnv → ProductionEnv
(verify) (production release)
- Reach a production release with the minimum number of environments
- Verify in TestEnv before deploying directly to ProductionEnv
Pattern 2 — Standard Setup
The recommended configuration for a typical development team.
DevelopEnv → StagingEnv → ProductionEnv
(dev/verify) (pre-prod check) (production release)
- Develop and verify in DevelopEnv, run final pre-release checks in StagingEnv, then release to ProductionEnv
- Running StagingEnv with production-equivalent settings lets you catch issues before they hit production
Pattern 3 — Full Setup
Suitable for multiple teams developing in parallel, or when quality and safety are the top priority.
TestEnv → DevelopEnv → StagingEnv → ProductionEnv
(trial) (dev/verify) (pre-prod check) (production release)
- Use TestEnv for demos and schema design exploration, then move to full development in DevelopEnv
- Complete acceptance testing in staging before promoting to production — the safest release workflow
Environment Independence
Each environment is fully independent and has the following characteristics:
- Data independence — Data is never shared across environments
- Version independence — Different versions of an API or WebUI can be deployed to each environment
- Operation independence — Upgrading in StagingEnv does not affect ProductionEnv
This allows development and verification to proceed in parallel while keeping the production environment safe.
See Upgrade and Rollback for details.