Environments¶
SchemAlign uses separate environments for production, test, and development work. This separation gives teams a safe place to build, validate, and review integration changes before they affect production users or production data.
Recommended environment model¶
For customer environments, SchemAlign recommends clear environment-specific hostnames. Users should see simple, recognizable URLs that identify the environment without exposing internal ports or server details.
Each hostname represents a distinct SchemAlign environment:
customer.schemalign.com -> production
customer-test.schemalign.com -> test
customer-dev.schemalign.com -> development
This keeps the user experience clean while preserving independent production, test, and development boundaries.
How SchemAlign separates environments¶
SchemAlign recommends that each environment have its own operational boundary. Production, test, and development should not share the same runtime resources.
Each environment should have separate:
- application services
- database
- artifact storage
- secrets and credentials
- OAuth/OIDC redirect URI
- session and cookie configuration
- worker queue namespace
- custom node runtime namespace
Why this matters¶
Environment separation protects production stability. Teams can test new pipelines, credentials, custom node changes, and workflow updates in a non-production environment before promoting them to production.
It also makes troubleshooting safer. A failed test run, development custom node change, or experimental pipeline should not affect production queues, production artifacts, production credentials, or production sessions.
SchemAlign recommendation
Treat production, test, and development as separate environments, not just separate URLs. The visible hostname should be easy for users to understand, and the underlying data, secrets, queues, artifacts, and runtime resources should remain isolated.