Bringing applications to life is an iterative and collaborative process, whether the application is developed by a single developer in the global community or a large team inside an organization.
It all starts with an idea. Perhaps a small change in an existing application or perhaps a completely new approach towards solving a problem. For most developers, deployment and operations are an obstacle, making it harder or even impossible to implement their ideas. For operations it is also a challenge, the faster the innovation the harder it is to provide a stable environment.
ElasticBox introduced its collaboration features to support this process. Our first iteration focused on open collaboration: it enabled anyone with direct access to a Box to make changes to it and made it easy for developers and operations to build Boxes together and make them available to others, directly or through workspaces.
This first iteration was great for a few people who work together but was difficult to scale. As more people get involved in a project, it becomes more important to control who can do what with Boxes and instances. That is why we are introducing more granular ways to share and define access levels for instances, Boxes, and providers.
Changes to Collaboration Capabilities
We are renaming “Collaboration” to “Sharing” and introducing a new access level. “Collaboration,” as we know it, will now be “Sharing with Edit Permissions.” In addition, we are introducing “Sharing View only.” This will let you share your assets with others without giving them the ability to make changes to those assets.
When you share a Box with Edit Permissions,
- Recipients will have access to and the ability to edit all versions of the Box
- Recipients will have access to and the ability to edit the current state of the Box
When you share a Box View only,
- Recipients will have access to but not the ability to modify all versions of the Box
- Recipients will not have access to the current state that you’re working on. This is a way to ensure distribution of stable, validated Boxes rather than unstable works in progress.
Sharing instances in View only mode enables some interesting use cases. For instance, developers can have access to a database in order to bind to their applications for testing, but not make any changes to the database. Sharing instances in Edit mode, on the other hand, is great if you need somebody to help you debug the Box or instance. For more information, please check out the product documentation.
These new features should make it easier for you and your teams to work together in a more efficient way! Another step towards enabling developers and operations to work together and move towards a DevOps culture!