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-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ 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](https://github.com/features/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.
8
+
Today, GitHub announced the private beta of [GitHub Codespaces](https://github.com/features/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
@@ -15,9 +15,9 @@ Describing development environments in code has many benefits:
15
15
16
16
- It eliminates onboarding friction: no matter if you are new to a project, need to go back to an old branch or just picking up development after a few weeks. Just go to your project and start coding immediately.
17
17
18
-
- Remote work becomes a breeze: now everyone can access source code more securely (no local copies) from any device, including Chromebooks and tablets.
18
+
- Remote work becomes a breeze: now everyone can access source code more securely (no local copies) from any device, including Chromebooks and tablets.
19
19
20
-
- Everybody gets the same setup: this means that “works on my machine” situations are a problem of the past.
20
+
- Everybody gets the same setup: this means that “works on my machine” situations are a problem of the past.
21
21
22
22
- With Gitpod, you can even take snapshots of any state of your dev environment and share exact clones of it.
23
23
@@ -29,7 +29,7 @@ As software systems become more complex so do dev environments. Have you ever tr
29
29
30
30
When we started working on Gitpod, we had everything running locally in minikube, too. Very quickly we realized that this would not scale. Our SaaS offering is deployed in Kubernetes clusters across the globe—that’s nothing you’d want to replicate locally.
31
31
32
-
For the past year the whole team has developed Gitpod in Gitpod. Everyone in the team can start coding on any branch immediately. That includes their own preview deployment which is already connected to and fully debuggable from their browser-based development environment. For a more in-depth look at our development pipeline—and what’s in it for you—check out [Chris’ talk](https://www.youtube.com/watch?v=dFMpXUsJcGM) (inlined below) and our [previous post](https://www.freecodecamp.org/news/developing-kubernetes-applications-with-joy/) on the matter.
32
+
For the past year the whole team has developed Gitpod in Gitpod. Everyone in the team can start coding on any branch immediately. That includes their own preview deployment which is already connected to and fully debuggable from their browser-based development environment. For a more in-depth look at our development pipeline—and what’s in it for you—check out [Chris’ talk](https://www.youtube.com/watch?v=dFMpXUsJcGM) (inlined below) and our [previous post](https://www.freecodecamp.org/news/developing-kubernetes-applications-with-joy/) on the matter.
33
33
34
34
`youtube: dFMpXUsJcGM`
35
35
@@ -45,7 +45,7 @@ Given all these benefits, you might wonder why no one did this earlier. After al
45
45
46
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
@@ -66,15 +66,15 @@ To also serve users beyond just GitHub, we have been focussing on integrating Gi
66
66
67
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
-
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.
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
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 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
-
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.
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
79
79
Experience the future of software development now!
Copy file name to clipboardExpand all lines: src/blog/gitpod-self-hosted-0.4.0.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ title: Gitpod Self-Hosted 0.4.0
6
6
image: /cloud-download.png
7
7
teaserImage: /cloud-download.png
8
8
---
9
-
We are excited to announce the new release of Gitpod Self-Hosted in version 0.4.0. Gitpod Self-Hosted allows everyone to set-up and run a service with the same features as gitpod.io in your cloud or corporate network.
9
+
We are excited to announce the new release of Gitpod Self-Hosted in version 0.4.0. Gitpod Self-Hosted allows everyone to set-up and run a service with the same features as gitpod.io in your cloud or corporate network.
10
10
11
11
### How Does it Work?
12
12
@@ -18,12 +18,12 @@ Gitpod Self-Hosted is truly self-hosted: it does not require an internet connect
18
18
19
19
Operating Gitpod in production on gitpod.io has enabled us to battle-harden this product at scale. Both offerings share the same codebase, hence offer the same qualities regarding scalability, cloud-density, reliability, and security. All improvements that we make on Gitpod’s SaaS offering directly benefit the self-hosted version.
20
20
21
-
This release ships a plethora of bugfixes and improvements, particularly in the area of GitLab integration.
21
+
This release ships a plethora of bugfixes and improvements, particularly in the area of GitLab integration.
22
22
There is one major feature that I want to show in more detail since you can't try this on gitpod.io:
23
23
24
24
### New Admin UI
25
25
26
-
This release ships with a new web UI for administrative tasks. The UI is particularly handy when providing support fo users.
26
+
This release ships with a new web UI for administrative tasks. The UI is particularly handy when providing support fo users.
27
27
It allows for easy listing and searching of users and worksapces.
28
28
When selecting a user, the UI will show the user's details and workspaces, as you can in the following screenshot:
Copy file name to clipboardExpand all lines: src/blog/open-vsx-in-gitpod.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Adoption from the tool-side is going well, too. We started by supporting Open VS
21
21
22
22
As you may already know, Gitpod lets you describe your dev environment as code. This means that you write configuration and code that makes Gitpod automatically generate ready-to-code dev environments for your project.
23
23
24
-
An important part of such a configuration is the set of IDE extensions you need. In Gitpod you have two choices, you can either
24
+
An important part of such a configuration is the set of IDE extensions you need. In Gitpod you have two choices, you can either
25
25
26
26
**[1] Install an extension for your project's dev environment, or**
Copy file name to clipboardExpand all lines: src/blog/opensource.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,16 +20,16 @@ Over the past year, Gitpod has simplified contributions to many open source proj
20
20
21
21
`youtube: dFMpXUsJcGM`
22
22
23
-
Naturally, we develop Gitpod in Gitpod. This allows the whole team to spin up fully initialized, remote dev environments on any branch at any time.
23
+
Naturally, we develop Gitpod in Gitpod. This allows the whole team to spin up fully initialized, remote dev environments on any branch at any time.
24
24
25
25
In line with the [pets vs. cattle](http://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/?utm_source=thenewstack&utm_medium=website&utm_campaign=platform) analogy of the cloud-native world, we treat dev environments as automated (yet customizable) resources you can spin up when you need them and close down (and forget about) when you are done with your task. Once you experience the peace of mind of automated, ephemeral dev environments you never want to go back.
26
26
27
-
Sven will run a webinar next week on Thursday, where we will showcase how we use Gitpod internally at Gitpod and how much it improves our workflow. Hope to see you there!
27
+
Sven will run a webinar next week on Thursday, where we will showcase how we use Gitpod internally at Gitpod and how much it improves our workflow. Hope to see you there!
28
28
29
29
30
30
<style>
31
31
.button {
32
-
background-color: #0087BE;
32
+
background-color: #0087BE;
33
33
border: none;
34
34
border-radius: 100px;
35
35
color: white;
@@ -61,7 +61,7 @@ Sven will run a webinar next week on Thursday, where we will showcase how we use
61
61
62
62
# Gitpod Self-Hosted is Now Free
63
63
64
-
The [SaaS offering of gitpod.io](https://www.gitpod.io/pricing/#) remains the easiest way to streamline your development workflows with continuously prebuilt dev environments.
64
+
The [SaaS offering of gitpod.io](https://www.gitpod.io/pricing/#) remains the easiest way to streamline your development workflows with continuously prebuilt dev environments.
65
65
66
66
In case you want to host Gitpod on your own infrastructure or private cloud, starting today, Gitpod Self-Hosted is free for unlimited users. Organizations using Gitpod Self-Hosted can purchase an enterprise license in order to get additional features like:
0 commit comments