Multi-Environment Deployments

We are excited to announce the release of our new feature: Multi-Environment Deployments. This update aims to enhance the safety and efficiency of developing and managing internal applications.

📚 Docs – Dive deeper into the setup and capabilities.

Importance of Multi-Environment Support

In internal application development, having multiple environments is essential to enable development teams to test new functionalities rapidly without affecting the production environment. With this release, Squadbase provides multi-environment support as a standard feature, making it simple to manage deployments across different environments.

Key benefits of this feature include:

• Reduced risk of disruptions in the production environment
• Ensured independence of development and testing environments
• Rapid feedback loops involving both developers and end-users

Detailed Feature Overview

The following environments are now provided by default:

• Production Environment: Dedicated environment for live operations.
• Preview Environment: For reviewing changes that do not yet have a linked GitHub branch.

In addition, users can create any number of additional custom environments.

Main functionalities:

• Ability to link GitHub branches to environments using exact or partial matching.
• Log monitoring support across all environments.
• User analytics functionality enabled exclusively in the Production environment for enhanced data protection.
• Automatic tracking of unlinked branches in the Preview environment, making them immediately accessible.

Shareable Links per Branch and Commit

With every new deployment, unique shareable links are automatically generated for each environment, branch, and commit. This enables developers to quickly and confidently review their changes in isolated environments, significantly streamlining the review and validation processes.

Example Workflow Using the New Feature

Here is an example workflow demonstrating how teams can leverage Squadbase's new multi-environment feature:

1. Developers create new branches and push changes to GitHub.
2. Changes are automatically deployed to the Preview environment, generating a unique URL.
3. Teams share the URL internally, enabling hands-on testing and gathering feedback, including from non-technical stakeholders.
4. If no issues arise, final integration testing is conducted in the Staging environment, after which changes are promoted to the Production environment.

Conclusion

Squadbase enables seamless progression of internal tools built with frameworks such as Streamlit and Next.js, from prototyping to production, providing scalability, stable operations, and continuous improvement to support organizational growth.

Deploying your internal tools to Squadbase takes only minutes. Sign up today and give it a try!