Download to read offline
Uploaded byLynn Langit
Understanding Codenvy - for Containerized Developer Workspaces
Codenvy provides containerized developer workspaces that allow for faster development in the cloud or on-premises. It aims to improve on current approaches like manual setup, desktop environments, and virtual machines that are administrative, error-prone, expensive, and not portable. Codenvy allows developers to modify, run, and debug code from anywhere through automated one-click provisioning of shareable and securely managed workspaces. It supports various programming languages and libraries through plug-ins and uses a factory/project model to create reusable templates and instances. Codenvy also enables contributions to open source through embedded buttons that allow direct code changes and pull requests on GitHub from within the Codenvy IDE.
More Related Content
Similar to Understanding Codenvy - for Containerized Developer Workspaces
![[Webinar] Automating Developer Workspace Construction for the Nuxeo Platform ...](https://cdn.slidesharecdn.com/ss_thumbnails/nuxeo-codenvywebinar-26-jan-2015-150205140757-conversion-gate02-thumbnail.jpg?width=640&height=640&fit=bounds)
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Understanding Codenvy - for Containerized Developer Workspaces
- 1. Understanding Codenvy @LynnLangitContainerized DeveloperWorkspaces June 2015
- 2. Current Approaches toDeveloper Workspaces... ● Manual: Step-by-step, administrative, & error-prone ● Desktop: Expensive, fixed size & not secure ● Virtualization: Large, slow, hard to synchronize & non- portable ...are not working
- 3. Contribute Your Codein Seconds Developer workspaces to modify, run and debug code in the cloud or on-premises DevOpsDevelopers Repeatable one-click automationVery Fast cloud-based IDE Provision developer workspaces that are simply shareable and securely managed Craft code, then command Docker-based microservices to run and debug from anywhere
- 4. Getting Started –Hello Codenvy
- 5. Get started withCodenvy Projects ● New: Open a Codenvy Template ● New: Import a GitHub Repo ● Existing: Click on a Codenvy Project URL
- 6. The Projects sectionallows you to: -- create an instance of existing project -- create a new project -- import a project
- 7.
- 8. Build / Run Features Clickthe blue link to open the view
- 9. Using Codenvy Factories& Projects
- 10. Use Supported Languagesand Libraries Plug Ins
- 11. Factory = Blueprint(JSON) Project = Instance Codenvy Objects
- 12. Enabling Developer Contributions “TheIntuit internal engineering hackathon on Codenvy supported 4000 engineers on 17 nodes, and they never installed a thing.” - Jeff Brewer, Distinguished Engineer, Intuit
- 13. Enterprise-Controlled Services Three-Tier ComposableServices Open Source Modules Composable Architectures -> Dependencies Modern Architectures include: Continuous Delivery Shifts operation burdens to development Microservices Increases setup, update and maintenance Containers Decomposes applications into modules
- 14. Dependencies -> Installation(Wiki) Nightmares Django and PHP with Eclipse Tomcat with IntelliJ Compile and install Ruby Mozilla Webmaker with Vagrant
- 15. GitHub Contribution Flow “Developersare looking for companies that not only use and contribute to open source, but also create a culture of open, community-style development.” -- Guy Martin, Samsung
- 16. Build Your ContributionFactory Build contribution factory Embed linked factory button into GitHub ReadMe file Track usage with Codenvy Analytics
- 17.
- 18. Click the buttonto open the pull request
- 19.
- 20.
Editor's Notes
- #3 Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- #4 Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- #6 Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- #12 http://docs.codenvy.com/user/factories/#what-are-factories http://docs.codenvy.com/project-lifecycle/ Projects To Create Factory Config New Project Wizard Import Project Project Template To Use Share or Embed Clone Destroy
- #14 Key point: Open source drives composibility, modularity and microservices
- #18 https://github.com/codenvy-demos/spring-petclinic
- #20 https://codenvy.com/products/pricing