Any
Core Studio Concept
Image Collaboration
KOS Studio is a collaborative environment. All instances of KOS Studio in an organization are synchronized in real time, ensuring changes propagate to the entire team instantly. Based on common use cases, KOS Studio provides three collaboration states: local, team, and production. Each one ensures you are using the correct artifacts and rules.
Local
Local image collaboration state provides the most flexibility. In this case mostly a developer is working in isolation to make the image work. Studio in local collaboration mode allows users to :
-
Configure the image to use local files. User can use these local files as “Local Artifacts” or “Layers”.
-
Configure the image to use local Override can be used for “Port Mappings” or for “Developer Flags”
-
Configure the image to use file mappings with local files.
Team
Team collaboration state enables developers to work in a team setting where one team member sets up the image and whole team uses the same image without needing to setup and remember all the settings/configurations. Studio in team collaboration mode allows users to :
-
Configure the image to use local files. User can use these local files as “Local Artifacts” or “Layers”.
-
Configure the image to use local Override can be used for “Port Mappings” or for “Developer Flags”
-
Configure the image to use file mappings with local files.
|
Team collaboration is the recommended state for working with KOS Studio as it provides the right balance between freedom of working in a development environment and collaboration features for teams. |
Production
The production collaboration state is the most restrictive state where the Studio ensures all the requirements for making an image ready for production are met. It will restrict users from using non-compliant artifacts in the images.
Once the image is set to production mode, the studio will only allow using, publishing, or marketing artifacts that are marked as production-ready. User need to choose a specific production KOS release. Any local artifacts, layers can only be referred if they are published and marked production ready.
Comparison
| Feature | Local | Team | Production |
|---|---|---|---|
KOS Version |
|
|
|
Port Mappings |
|
|
|
Developer Flags |
|
|
|
Local Artifacts |
|
|
|
Layers |
|
|
|
File Mappings |
|
|
|
On this page
Java Development
Seamlessly transition from Legacy+ systems to Freestyle microdosing and advanced distributed dispense systems.
UI Development
Using KOS SDKs, integrating Consumer and Non-consumer facing UIs becomes seamless, giving you less hassle and more time to create.
Video Library
Meet some of our development team, as they lead you through the tools, features, and tips and tricks of various KOS tools.
Resources
Familiarize yourself with KOS terminology, our reference materials, and explore additional resources that complement your KOS journey.
Copyright © 2024 TCCC. All rights reserved.
