You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 19, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: src/blog/github-codespaces.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
date: Wed May 06 2020 19:00:00 GMT+0000 (UTC)
2
+
date: Wed May 06 2020 16:00:00 GMT+0000 (UTC)
3
3
author: svenefftinge
4
4
subtitle: A Milestone for Automated Development Environments
5
5
title: GitHub Codespaces, Welcome to the Party!
6
6
image: /gh-cs-bg.jpg
7
7
---
8
-
Today, GitHub announced the private beta of GitHub Codespaces which provide container-based dev environments for GitHub projects. At Gitpod, we are building a similar solution and while GitHub’s Codespaces don’t fully implement everything we do, they embrace the notion of dev environments as code.
8
+
Today, GitHub announced the private beta of GitHub Codespaces, which provide container-based dev environments for GitHub projects. At Gitpod, we are building a similar solution, and while GitHub’s Codespaces don’t fully implement everything we do, they truly embrace the notion of dev environments as code.
9
9
10
10
This is great news, because it really helps to explain why this is going to change professional software development entirely.
11
11
@@ -43,9 +43,9 @@ Once dev environments have become code you can pre-build those dev environments
43
43
44
44
Given all these benefits, you might wonder why no one did this earlier. After all, developers automate the world on a daily basis. Thinking about it, it’s strange that most developers still set things up manually before they can get down to business.
45
45
46
-
There have been attempts to automate dev environments in the past (e.g. Docker, Vagrant, Cloud9). These early approaches always came with too many compromises and their benefits did not quite outweigh the drawbacks. The biggest blocker was that developers could no longer use the powerful tools they normally would, most importantly an awesome Editor/IDE.
46
+
There have been attempts to automate dev environments in the past (e.g. Docker, Vagrant, Cloud9). These early approaches always came with too many compromises, and their benefits did not quite outweigh the drawbacks. The biggest blocker was that developers could no longer use the powerful tools they normally would, most importantly an awesome Editor/IDE.
47
47
48
-
This has changed since with VS Code a web-technology based IDE has become so popular among developers. However, Microsoft has not open-sourced the browser version of VS Code. For GitHub, a Microsoft-owned company, this is obviously not an issue. For everyone else we have developed Eclipse [Theia](https://dev.to/svenefftinge/theia-1-0-finally-a-good-browser-ide-3ok0).
48
+
This has changed since, with VS Code, a web-technology based IDE has become so popular among developers. However, Microsoft has not open-sourced the browser version of VS Code. For GitHub, a Microsoft-owned company, this is obviously not an issue. For everyone else we have developed Eclipse [Theia](https://dev.to/svenefftinge/theia-1-0-finally-a-good-browser-ide-3ok0).
49
49
50
50
Theia provides the same functionality as VS Code, even supports VS Code extensions, and comes with an architecture that allows everyone to customize the IDE easily. It is developed as a true open-source, vendor-neutral project at the Eclipse Foundation *) and is adopted by Google, IBM, RedHat, SAP, arm, Arduino and many more. Mike Milinkovich wrote about the [differences between Theia and VS Code](https://blogs.eclipse.org/post/mike-milinkovich/eclipse-theia-and-vs-code-differences-explained) recently.
51
51
@@ -60,19 +60,19 @@ We are thrilled to see GitHub/Microsoft investing in automated development envir
60
60
61
61
But most professional development happens on other platforms such as GitLab, Atlassian’s stack and of course good old GitWeb. Oftentimes companies even employ a mixture of these.
62
62
63
-
To also serve users beyond just GitHub, we have been focussing on integrating Gitpod with other platforms as well. In December we released support for GitLab and integration with Atlassian’s Bitbucket (and Jira) will be available soon.
63
+
To also serve users beyond just GitHub, we have been focussing on integrating Gitpod with other platforms as well. In December we released support for GitLab, and integration with Atlassian’s Bitbucket (and Jira) will be available soon.
64
64
65
65
### Closer to Home: Gitpod Self-Hosted
66
66
67
-
Chances are that you host your Git repositories or other dev infrastructure in a private cloud or on a local network where they can not be accessed from the outside. Thus, a hosted IDE service must be on the same private cloud or network. This is possible with [Gitpod Self-Hosted](/self-hosted) which can be installed on Kubernetes and does not require a connection to the public internet.
67
+
Chances are that you host your Git repositories or other dev infrastructure in a private cloud, or on a local network where they can't be accessed from the outside. Thus, a hosted IDE service must be on the same private cloud or network. This is possible with [Gitpod Self-Hosted](/self-hosted/) which can be installed on Kubernetes and does not require a connection to the public internet.
68
68
69
69
Today we are releasing a new version which brings Gitpod Self-Hosted on par with Gitpod.io. The new release includes better GitLab integration and a new admin UI. With Gitpod Self-Hosted you can now enjoy this liberating way of developing software with your own GitLab installation.
70
70
71
-
**Gitpod Self-Hosted is entirely free for up to five users and a free trial month for unlimited users is available, too.**
71
+
**Gitpod Self-Hosted is free for up to five users, and a free trial month for unlimited users is available, too.**
72
72
73
73
### Summary
74
74
75
-
We are quickly headed into a wonderful future, where developers are no longer intimidated by tedious and outdated setup procedures. Professional software projects will provide automated, prebuilt development environments that will enable teams to start contributing, doing code reviews, reproducing bugs or just exploring new ideas immediately from any device securely.
75
+
We are quickly headed into a wonderful future, where developers are no longer intimidated by tedious and outdated setup procedures. Professional software projects will provide automated, prebuilt development environments that enable teams to start contributing, doing code reviews, reproducing bugs or just exploring new ideas immediately from any device securely.
76
76
77
77
CI/CD has taught us how versioned, reproducible infrastructure as code is key to scale modern software development. Now it is time to apply these lessons to our development environments and furthermore improve our lead times getting from ideas to production.
78
78
@@ -83,4 +83,3 @@ Experience the future of software development now!
0 commit comments