Environments¶
Environments in Omnistrate provide isolated, configurable deployment contexts that enable you to manage different stages of your software development lifecycle. They serve as the foundation for implementing robust deployment pipelines, testing strategies, and production operations.
Each environment serves a specific purpose in the software development lifecycle, allowing for controlled testing and validation of code changes before they are promoted to the next stage or, ultimately, to production. Omnistrate automates the whole process to deliver an efficient and reliable software delivery pipeline from promotions across environments, access control etc.
Overview¶
Omnistrate environments are logical groupings of infrastructure and configuration that allow you to:
- Isolate Workloads: Separate development, testing, staging, and production deployments
- Control Access: Implement role-based access controls per environment
- Enable Promotions: Facilitate automated and manual deployment promotions between environments
- Manage Configurations: Apply environment-specific configuration
- Ensure Consistency: Maintain configuration parity while allowing environment-specific customizations
Environment Types¶
Development Environment¶
This is where software developers work on new features or bug fixes. It typically mirrors the developer's local development environment and may include development databases, code repositories, and development tools.
Testing Environment¶
The testing environment is used for quality assurance and automated testing. It is designed to mimic the production environment as closely as possible to identify potential issues before code is deployed to production.
Production Environment¶
The production environment is where the live application or service is hosted and accessed by end-users. It is the final destination for code changes after they have been tested and approved in previous environments.
Sandbox Environment¶
Developers may create temporary environments for working on specific features or bug fixes in isolation before merging their changes into the main development branch.
Access Control¶
You can choose to enable specific access controls to restrict who can enable promotions across environments. See more information about promotion pipelines here
Going live with your SaaS Product¶
Production environments can be made Public to make your SaaS Product available to your customers. Omnistrate provides Customer Portal - ready to use Web Application - for your end customers. Once you have made an environment public and configured Customer Portal, your SaaS Product will be available on your custom domain for your customers to use. To configure custom domain, please refer to the following link