<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Gitpod - Medium]]></title>
        <description><![CDATA[Always ready-to-code. The developer platform for on-demand cloud development environments to create software faster and more securely. - Medium]]></description>
        <link>https://medium.com/gitpod?source=rss----f9406e1af61f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Gitpod - Medium</title>
            <link>https://medium.com/gitpod?source=rss----f9406e1af61f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:09:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/gitpod" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Status Update: Gitpod ❤️ Statusfy]]></title>
            <link>https://medium.com/gitpod/status-update-gitpod-%EF%B8%8F-statusfy-ed8266d63a20?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed8266d63a20</guid>
            <category><![CDATA[statusfy]]></category>
            <category><![CDATA[gitpod]]></category>
            <category><![CDATA[status-page]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Christian Weichel]]></dc:creator>
            <pubDate>Tue, 29 Jan 2019 14:10:50 GMT</pubDate>
            <atom:updated>2019-01-29T14:22:35.985Z</atom:updated>
            <content:encoded><![CDATA[<p>A core value at Gitpod is transparency: a lot of what we do is out in the open, because we believe that that’s the best way to earn the trust of our users. Until recently there was one point where we had <a href="https://github.com/gitpod-io/gitpod/issues/130">some catching up</a> to do in that regard: <a href="https://status.gitpod.io/">having a status page</a>.</p><p>We had three main requirements for our status page:</p><ul><li>It had to be <strong>rock solid</strong> because if your status page is not available, how am I going to trust your product?</li><li>It should <strong>present the status of our service, nothing else</strong>. We already have an extensive monitoring setup (based on Prometheus/Grafana/InfluxDB) that watches over our infrastructure. No need to introduce yet another monitoring solution. A surprising amount of status page projects also do monitoring/health checks on the side.</li><li>It had to <strong>integrate into our existing infrastructure</strong>. If we could use Git, our existing cloud infrastructure and Gitpod to update/manage our incident reports, all the better. We already have this infrastructure in place, so if we could avoid setting up a brand new website deployment, that is a plus.</li></ul><p>Our <a href="https://github.com/gitpod-io/gitpod-docs">documentation</a> and website are statically generated from Markdown which we edit using Gitpod, push to GitHub and build/deploy using Jenkins. This pattern works well for us, it would be nice if we could use the same process for our status page.</p><h3>Hello Statusfy</h3><p>Enter <a href="https://statusfy.co/">Statusfy</a>, an Open Source status page system that can render the status page statically or dynamically from Markdown files. It sports a wide range of deployment options, including pushing the statically generated files to a <a href="https://cloud.google.com/storage/docs/key-terms#buckets">GCP bucket</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8yRrsPnasOhAbZ9CbsTTIg.png" /></figure><p>Turns out that Gitpod and Statusfy are perfectly complementary. Say we just found an issue and want to update the status page, the steps are as simple as:</p><ol><li>Open the <a href="https://github.com/gitpod-io/gitpod-status">gitpod-status</a> repository in Gitpod</li><li>Create a new incident using yarn new-incident</li><li>Preview the incident to make sure everything looks alright</li><li>git commit &amp;&amp; git push which has Jenkins pick up the changes, re-generate the status page and push it to the Google Bucket.</li></ol><p>This setup ticks all boxes: it’s rather solid (GCP buckets have a decent track record), deals with incidents and incidents only, and fits well in our existing infrastructure.</p><h3>Getting started</h3><p>It took us only a couple of hours to build our status page using Statusfy. In part that’s because we had a few things in place already, but mainly because Gitpod and Statusfy make for a great team.</p><p>If you want to replicate this setup at home, create a repo on GitHub, open Gitpod on that repo and run npx statusfy init. The next steps and deployment options are described in Statusfy’s excellent <a href="https://docs.statusfy.co/guide/getting-started.html#installation">Getting Started guide</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed8266d63a20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/status-update-gitpod-%EF%B8%8F-statusfy-ed8266d63a20">Status Update: Gitpod ❤️ Statusfy</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sustainable Node.js development with only a browser]]></title>
            <link>https://medium.com/gitpod/sustainable-node-js-development-with-only-a-browser-4887bc6e737b?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/4887bc6e737b</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Anton Kosyakov]]></dc:creator>
            <pubDate>Fri, 14 Dec 2018 13:07:59 GMT</pubDate>
            <atom:updated>2018-12-14T13:07:59.373Z</atom:updated>
            <content:encoded><![CDATA[<p>Nowadays, there are many collaborative platforms for showcasing JS code snippets and frameworks. Most of them run in your browser, some even manage to magically run Node.js applications in the cloud. They abstract away many possibilities in order to focus on prototyping and learning.</p><p>This simplification (or even magic) eventually turns out to be a hard wall. Once we leave the prototype stage, we need to be able to control and freely combine different versions of frontend and Node.js frameworks, connect to the database that best fits our use case, use different JS flavors and deployment services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zkVCKjkjvyutzD5hFn_Tw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/fQxMGkYXqFU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clark Young</a> on <a href="https://unsplash.com/search/photos/%22workshop%22?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In this blog post, I will show you a transparent way of getting started with Node.js easily without the magic. The approach taken provides a low entry barrier without the wall once you grow out of it. You will learn how to write Node.js applications in a browser-based environment, that has all the depth of a full local dev environment with VS Code but the friendly onboarding of JSFiddle. These environments can be freely shared to work together and showcase your applications.</p><p>The dev environment is called <a href="https://www.gitpod.io/">Gitpod</a> and is entirely free for open-source development.</p><h4>Table of Contents</h4><ul><li><a href="https://medium.com/p/4887bc6e737b#b85f">Hello World</a></li><li><a href="https://medium.com/p/4887bc6e737b#8154">Automating Node.js setup</a></li><li><a href="https://medium.com/p/4887bc6e737b#1bc9">Working with Pull Requests</a></li><li><a href="https://medium.com/p/4887bc6e737b#77a3">Working Together</a></li><li><a href="https://medium.com/p/4887bc6e737b#84df">Developing full-stack Node.js applications</a></li><li><a href="https://medium.com/p/4887bc6e737b#8c36">Summary</a></li></ul><h3>Hello World</h3><p>Let’s get started by developing a simple “Hello World” application and learning the basics of Node.js development.</p><h4>Start a new project</h4><p>Gitpod treats any GitHub repository as a project which can be opened. Let’s start by creating a new repository for our Hello World project:</p><ul><li>open your GitHub dashboard and select New Repository;</li><li>enter a repository name and click Create repository.</li></ul><p>Now, we can open the created project in Gitpod. You can do it by simply prefixing the repository URL with gitpod.io#. For example, I’ve called my repository node-hello-world and it can be opened in Gitpod with <strong>gitpod.io#</strong>https://github.com/akosyakov/node-hello-world.</p><p>The first time, you will need to sign in Gitpod with your GitHub account. GitHub will ask you to authorize read access to your email address. Write access to repositories can be granted later on <a href="https://gitpod.io/access-control/">your access control page</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8cn3G30eQouKmWQb228LQ.png" /></figure><p>Gitpod starts a new workspace, which is a Linux-based cloud container, and provides access to it via a VS Code powered online IDE. Workspaces are started on demand and automatically shut-down if you don’t use them. They are continuously replicated and never deleted, so you always can restart a workspace later from <a href="https://gitpod.io/workspaces/">your Gitpod dashboard</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXM-VDzzmpXCvlAVvQIjVw.gif" /></figure><p><em>If you don’t want to create a new project from scratch, click on </em><a href="https://gitpod.io/#snapshot/0d82ae08-c328-4cb5-96e5-7233d5de0c11"><em>a snapshot link</em></a><em> of my workspace to try Hello World application. I will cover later how one can make a workspace snapshot.</em></p><h4>Writing a Node.js application</h4><p>By default, each workspace is preconfigured with standard tools like Node.js, npm, yarn and nvm. Later we will learn how to change the Node.js setup. Now, let’s code something and run it:</p><ul><li>open the command palette (F1) and select New File command;</li><li>create a new file with app.js name and type the following content:</li></ul><pre>const message = &#39;Hello World&#39;;</pre><pre>console.log(message, &#39;from Gitpod!&#39;);</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b-63v0Asfa09vfzG" /><figcaption>As you type, you can see that Gitpod validates your code. It also provides you with smart completions and documentation on hover.</figcaption></figure><h4>Run / Debug a Node.js application</h4><p>In order to run the application, type node app.js into the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*KzrRQ41oARG7XoQB" /></figure><p>Of course, you can have more than one terminal to your cloud workspace.</p><p>Next up, let’s see how we can debug the application:</p><ul><li>create a debug configuration (Debug-&gt; Add Configuration) and select Node.js: Launch Program configuration snippet in the content assist of the opened editor;</li><li>add a breakpoint into app.js file, by clicking on the gutter on the left;</li><li>open the Debug View (View -&gt; Debug),</li><li>press the green play icon to start debugging (or press F5).</li></ul><p>Our program should run, and when a breakpoint hits you can inspect call stack, variables and even use the debug console to evaluate expressions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VHUqe81CKwdHq7uK" /></figure><h4>Working with Git</h4><p>Let’s have a look at how we can share our changes through Git. Open the Git view, stage your changes, enter a commit message and click commit. You can also open a diff editor by clicking on changed files and push new commits to GitHub with Git: Push... command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FqWgZy08qIkj3qVp" /></figure><p>If you have not granted write access to your repositories yet, Gitpod will ask for it. Grant permissions and try to push again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHchL7DVfmfdYWqjWsqRaw.png" /></figure><h3>Automating Node.js setup</h3><p>As mentioned above each workspace by default is preconfigured with standard tools, like Node.js 8.x.</p><p>Let’s assume that we agreed on using Node.js 10.x for our project instead. Usually, all developers have to update their local Node.js versions and often switch between them depending on what project or branch is used.</p><p>With Gitpod, it is different. You can configure a workspace with a specific Node.js version for each branch via Docker images, without changing the local setup for any developer at all.</p><p>The easiest way to initialize the config is to use Gitpod’s CLI. The CLI will walk you through the most important configuration options and create a .gitpod.yml file that is located in the root of your repository.</p><p>In the terminal type gp init.</p><ol><li>For the first option choose: docker file. It will create a Dockerfile that sits next to .gitpod.yml. Here you can add any kind of tools and dependencies you will need for development. When starting a fresh workspace, Gitpod will pick that Dockerfile up and provide a cloud container based on that.</li><li>Now press enter until the tasks section. Type node app.js. The tasks are automatically started whenever a workspace gets started. You can have multiple tasks and use different lifecycles. Each task will be opened in a separate terminal.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*yVXQ8QGJEmCnNQ52" /></figure><p>The created files will be automatically opened in the editor. Let’s change the config so that it starts two tasks in separate terminals:</p><pre>image:</pre><pre>  file: Dockerfile</pre><pre>tasks:</pre><pre>  - init: node --version</pre><pre>  - command: node app.js</pre><p>And change the Dockerfile to use Node.js 10.x as the base image:</p><pre>FROM node:10</pre><p>To try it our we need to push the config back to GitHub and open a new workspace. Let’s do this through a pull request, so we learn about the GitHub integration on the way.</p><p><em>Here is </em><a href="https://gitpod.io/#snapshot/ea0d6704-a513-4c94-b8e7-fe72c3d8e5fb"><em>another snapshot link</em></a><em> to try our configuration without opening a pull request. You can learn more about workspace configuration </em><a href="https://docs.gitpod.io/40_Configuration.html"><em>here</em></a><em>.</em></p><h3>Working with Pull Requests</h3><p>Gitpod provides seamless integration with GitHub features like creating and reviewing pull requests.</p><h4>Creating a new Pull Request</h4><p>Let’s open a new pull request from Gitpod:</p><ul><li>commit your changes using the Git view (see above);</li><li>use Git: Checkout command or click the branch item in the status bar to create a new branch. Name it somehow, e.g. gitpodify;</li><li>next up open the Pull Request view on the right. You cannot create a new pull request yet, because first the new branch should be published to GitHub, click publish changes;</li><li>after that, the Pull Request view will be updated and you can open a new pull request.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vHysVOgVJaH6-j1t" /></figure><h4>Reviewing a Pull Request</h4><p>As I’ve mentioned at the beginning Gitpod treats each GitHub repository as a project. Actually, it is even smarter and can figure out from any GitHub URL which branch should be opened and how.</p><p>Let’s go to the pull request page on GitHub and prefix its URL with gitpod.io#, just like we did initially:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YXS_V_quV3Lg7Y-X" /><figcaption>Opening a PR with new workspace image can take some time since Gitpod needs to build the image. But it is only rebuilt when changed.</figcaption></figure><p>As you can see, Gitpod opens with a branch for your pull request. PR file changes are presented on the left sidebar to review. Our init and command workspace tasks are executed in terminals, Node.js is 10.x now, and Hello World is printed.</p><p>While reviewing in Gitpod, you can comment, change the code to address comments, suggest new changes, etc. When you are done, merge your pull request from Gitpod as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KIZkXiyQv3aZzsjA" /></figure><h3>Working Together</h3><p>Since Gitpod workspaces are running in the cloud, we can share them in similar ways how you share documents in Google Docs.</p><h4>Helping others with Node.js development</h4><p>You can share you running workspaces with colleagues to collaborate on exactly the same codebase, development tools, running terminals, and applications. It is particularly useful to assist each other on some tricky configuration, dependency or code problem.</p><p>In order to share a running workspace: click on your account avatar, select Share Running Workspace, enable sharing, copy a link and share the copied link with your colleagues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yp7USviOYhUm_P40" /><figcaption>Both users use exactly the same workspace and see the shared output in terminals.</figcaption></figure><h4>Showcasing Node.js applications</h4><p>You can take a complete snapshot (clone) of your workspace, even including your IDE layout, and share it as a link. Think about workspace snapshots like code snippets on JSFiddle. It is useful in the same way: to share reproducible examples on issues, Stack Overflow answers, for tutorials and workshops. But at the same, you share the complete development setup and present it in the appropriate way.</p><p>In order to share a workspace snapshot: click on your account avatar, select Share Workspace Snapshot, copy a link and share the copied link where you want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-n2I6-4fPuKK70_5" /><figcaption>The <a href="https://gitpod.io/#snapshot/14dc69f1-0e8c-4a36-b221-0ab16e91326e">shared workspace snapshot</a> preserves not only the development setup but the IDE layout and even selection in the editor.</figcaption></figure><h3>Developing full-stack Node.js applications</h3><p>So far, we’ve only had a look at a simple Node.js application. In case you wonder whether it will scale to sophisticated applications you can try any of the following repositories:</p><ul><li><a href="https://github.com/gitpod-io/nodejs-shopping-cart">Node.js Shopping Cart</a> is a reference Node.js application demonstrating how to use the Express framework. You can open it in Gitpod with <a href="https://gitpod.io/#https://github.com/gitpod-io/nodejs-shopping-cart">one-click</a> and follow along <a href="https://medium.com/gitpod/debugging-node-js-applications-in-theia-76c94c76f0a1">this blog post</a> explaining in details how to debug the app.</li><li>Gitpod is based on an open-source IDE framework — <a href="http://theia-ide.org/">Theia</a>. It’s built with a lot of JS technologies, including Node.js, Express, TypeScript and React. And, of course, <a href="https://github.com/theia-ide/theia/blob/master/doc/Developing.md#run-the-browser-example-with-gitpod">Gitpod is used to develop Theia</a>.</li><li>You even can develop Electron applications in Gitpod, like VS Code. Chris demonstrates it in <a href="https://medium.com/gitpod/developing-native-ui-applications-in-gitpod-15af2967c24e">this blog post</a>.</li></ul><h3>Summary</h3><p>Gitpod provides the complete Node.js development experience right from a browser. It enables you to automate your development setup, quickly onboard developers, streamline code review and testing processes on GitHub, help each other in real time, showcase your applications and setups. Also, it is entirely free for open source development!</p><p>If you have any questions, <a href="https://spectrum.chat/gitpod">join Gitpod Community on Spectrum</a>! We are listening intensely to all feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4887bc6e737b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/sustainable-node-js-development-with-only-a-browser-4887bc6e737b">Sustainable Node.js development with only a browser</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code never lies — Creating reproducibles for any programming language]]></title>
            <link>https://medium.com/gitpod/code-never-lies-creating-reproducibles-for-any-programming-language-7946021a68f2?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/7946021a68f2</guid>
            <category><![CDATA[jsfiddle]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[stackoverflow]]></category>
            <category><![CDATA[codepen]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Sven Efftinge]]></dc:creator>
            <pubDate>Thu, 29 Nov 2018 15:25:00 GMT</pubDate>
            <atom:updated>2018-11-29T16:12:33.512Z</atom:updated>
            <content:encoded><![CDATA[<h3>Code never lies — Creating reproducibles for any programming language</h3><p>Whenever you want to share a reproducible example on StackOverflow or an issue report, providing real code that can be quickly tried, executed and explored is the best you can do. Online code playgrounds, such as CodePen or JSFiddle, are an excellent way to do that, as they are very accessible for both the creator and the readers. Unfortunately, they are not available for every programming platform, language and often don’t work for larger projects or examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xIYVtetr9mExEzBd" /><figcaption>Photo by <a href="https://unsplash.com/@hannahj236?utm_source=medium&amp;utm_medium=referral">Hannah Jacobson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In this post I’d like to introduce you to a new feature in <a href="https://gitpod.io/">Gitpod</a>, that lets you create reproducible examples for any programming environment and any size of project.</p><h3>New in Gitpod: Snapshots</h3><p>No matter what state your Gitpod workspace is in, taking a Snapshot captures everything and provides you a link to share anywhere: on issues, forums (StackOverflow), emails and blogs. Anybody who clicks on a snapshot link instantly gets an exact copy of that workspace, including any uncommitted file changes and the UI layout.</p><p>Let’s go through an example.</p><h4>Spring Boot Example</h4><p>I went over to <strong>spring-boot</strong> and picked the first issue in the list:</p><p><a href="https://github.com/spring-projects/spring-boot/issues/15326">Bean overriding in spring boot 2.1 · Issue #15326 · spring-projects/spring-boot</a></p><p>The issue has a detailed description on how to reproduce the problem. It even has a link to a GitHub repository containing the code! So the author did a lot to make it easy for the maintainers to reproduce the issue and figure out what’s wrong.</p><p>However, instead of laying out the steps in prose, an automated solution would be much better. A snapshot would have reduced this to a single click for the maintainers, and the author wouldn’t have to write a lengthy explanation.</p><h4>Take a Snapshot</h4><p>Before we are taking the snapshot, we want to make sure everything is in the state we want it to be. So the maintainers get pointed to the culprit immediately. For this example I made sure</p><ul><li>the build ran through,</li><li>the right editors are opened <br>(I choose to open the two files mentioned in the issue in split mode),</li><li>the sample application is started automatically</li></ul><p>Taking care of the first two items is easy. For the third, you need to add a <strong><em>.gitpod.yml</em></strong> to the root of the project containing the tasks you want to start.</p><p>In the case of this project I added a task to start the failing Java process:</p><pre>tasks:<br> - command: &gt;<br>    mvn -q exec:exec \<br>        -Dexec.executable=java \<br>        -Dexec.args=”-cp %classpath com.example.beanoverriding.EmbeddedApplication” \ <br>        -Dexec.classpathScope=”test”</pre><blockquote>Btw. to figure out how to start that damn thing using Maven, I had to ask the community on StackOverflow. Of course, by providing a Gitpod Snapshot :-)</blockquote><p><a href="https://stackoverflow.com/questions/53536751/run-main-from-test-scope-in-maven-the-parameters-mainclass-for-goal-org-code">Run main from test scope in Maven: &quot;The parameters &#39;mainClass&#39; for goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java are missing or invalid&quot;</a></p><p>With the <strong>.gitpod.yml </strong>configured and the editors and views laid out as needed, we are ready to take a snapshot. Simply click on the avatar on the top right:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nOXkwor5kPsdJb-o2oHy4w.png" /></figure><p>Pick “Share Workspace Snapshot” and copy and share the link or one of the snippets in the opened dialog:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aDOY4sHSyefz2uepzGskw.png" /></figure><p>Here’s the snapshot link for you to try: <br><a href="https://gitpod.io/#snapshot/f7f5954a-250b-4113-909c-aae88b64321c">https://gitpod.io#snapshot/f7f5954a-250b-4113-909c-aae88b64321c</a></p><h3>Summary</h3><p>Gitpod Snapshots are a very convenient way to create and consume large and small examples for any programming language and platform. Make sure to check out the <a href="https://docs.gitpod.io/">documentation</a>, which goes into more detail on the options available.</p><p>We think snapshots are not only great for reproducing issues or showing solutions and examples, but very useful in other situations. Preparing workshops and tutorials should be super convenient with snapshots, as it will free your audience from any tedious setup procedures. We are looking forward to learning about all the creative ways you will put this feature to use. Please <a href="https://github.com/gitpod-io/gitpod">let us know</a> and have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7946021a68f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/code-never-lies-creating-reproducibles-for-any-programming-language-7946021a68f2">Code never lies — Creating reproducibles for any programming language</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debugging Node.js applications in Theia]]></title>
            <link>https://medium.com/gitpod/debugging-node-js-applications-in-theia-76c94c76f0a1?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/76c94c76f0a1</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[gitpod]]></category>
            <category><![CDATA[theia]]></category>
            <dc:creator><![CDATA[Anton Kosyakov]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 17:39:13 GMT</pubDate>
            <atom:updated>2018-11-15T17:39:12.624Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.gitpod.io/">Gitpod</a> is based on the open-source <a href="http://theia-ide.org/">Theia IDE Framework</a>, which is highly inspired by VS Code, reuses its major components like the Monaco editor and intelligent-language support and is designed to run as a web application.</p><p>At TypeFox, we use Gitpod to develop Theia and all its satellite projects, like Theia extensions and language servers. We’ve discovered that for most use cases we don’t need to go to local development anymore. Development, testing, and the review processes are streamlined, leading from source code to a proper development environment accessible from a browser with a single click.</p><p>Up to now, there was one important use case that forced us back to local tools, because it was not supported by Gitpod: Debugging.</p><p>Now, it is available, and I would like to give you a run through the basics of Node.js debugging in Gitpod based on an example.</p><h3>Step 0: Open Node.js Shopping Cart example in Gitpod</h3><p>Start a new workspace for the example GitHub repository: <a href="https://gitpod.io/#https://github.com/gitpod-io/nodejs-shopping-cart">https://gitpod.io#https://github.com/gitpod-io/nodejs-shopping-cart</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WySkgfqLHyOkQq_c" /></figure><p>A new Gitpod workspace will be opened. Required dependencies are installed automatically since the repository is configured with <a href="https://docs.gitpod.io/40_Configuration.html">a .gitpod.yml file</a>. You can see it in the terminal, opened in the bottom area.</p><h3>Step 1: Start debugging</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*cm6tolHouEztvvuC" /></figure><p>In order to start debugging, you should open the debug view first. You can do it via Viewmain menu or with Ctrl/Cmd+Shift+D.</p><p>The debug view allows you to configure launch configurations, start and manage debug sessions. Configurations are persisted debugging setups. They are stored in a <a href="https://code.visualstudio.com/docs/editor/debugging#_launchjson-attributes">VS Code compatible format</a> in a launch.json JSON-file located in your workspace’s .theia folder. If your project already has the VS Code launch file, then Gitpod will recognize and use it instead.</p><p>Node.js Shopping Cart is an Express.js web-application. The repository already has a pre-configured Launch Program configuration, which starts the web server Node.js process in the debug mode. Let’s run it with F5 or by pressing the run button left to the configuration drop-down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUD-Cfy3YC86JJmgo1bLpA.png" /></figure><h3>Step 2: Preview the application</h3><p>A notification should pop-up suggesting you open an application side-by-side with an editor or externally, in a new browser tab. Let’s open it side-by-side to be able to debug and use our app at the same time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65SBIeZyvn_31V9biYKNAQ.png" /></figure><p>Take your time and play with the app. You can review items to buy and in your cart, move them into or out of your cart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6KN6axYYOW8iqlnqsXpVw.png" /></figure><h3>Step 3: Pause on a breakpoint</h3><p>In this step we debug what happens when a user navigates to the homepage.</p><p>First, we need to add a breakpoint to the routing logic. It is defined in routes/index.js. You can open that file from the navigator or using the quick file palette (Ctrl/Cmd+P) .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ni4GKFo9FFJoh_r8lvLVg.png" /></figure><p>Next, add a breakpoint in the editor margin against a line which you want to debug. A route callback handling / path looks promising.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AaqYqH5LILFw4g0-jNu5Bg.png" /><figcaption>Breakpoints are displayed in the debug view and applied to currently running sessions.</figcaption></figure><p>Now, in the app, try navigating to the homepage. The debug session will pause on the breakpoint. You can traverse the current stack trace, inspect variables and control the execution flow with the debug actions toolbar:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Ru0MXHEcU_RzQEAKX30seA.png" /></figure><h3>Step 4: Inspect and modify data</h3><p>There are several ways to see variables’ values:</p><ul><li>you can traverse current scopes and variables in the debug view;</li><li>you can hover over expressions in the editor to evaluate them with a current session;</li><li>or you can use the debug console (REPL) to evaluate custom expressions.</li></ul><p>You can always double-click on any variable to modify its value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_zf4PL_AWfzeBZlp2mRjZQ.png" /></figure><h3>Next steps</h3><p>Debugging is an important feature to provide the complete development experience. The Node.js debugging support is the first step for Gitpod in this direction. We are working to bring more debug features and add support for more runtimes. We would also love to hear what features and runtimes you want to see supported. <a href="https://github.com/gitpod-io/gitpod/issues/new/choose">Tell us</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c94c76f0a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/debugging-node-js-applications-in-theia-76c94c76f0a1">Debugging Node.js applications in Theia</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing native UI applications in Gitpod]]></title>
            <link>https://medium.com/gitpod/developing-native-ui-applications-in-gitpod-15af2967c24e?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/15af2967c24e</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[gitpod]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Christian Weichel]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 09:27:59 GMT</pubDate>
            <atom:updated>2018-10-05T14:22:51.682Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.gitpod.io/">Gitpod</a> is a web-based IDE. As such one would think it only works for web-based projects or anything else that does not require a native UI. However, there’s still a plethora of native UI applications around and many of them are here to stay. In this article we’ll go through how to use Gitpod for developing native desktop UI applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YaZqFJXHopwW0puvvmfEew.png" /></figure><p>A few days ago <a href="https://medium.com/gitpod/bring-your-own-docker-image-to-gitpod-52db1aa861de">Gero introduced Docker builds to Gitpod</a> with which you can bring your own Dockerfile (instead of a pre-built image), and Gitpod will build the image for you. We’ll use that feature to setup a cloud-based development environment for native UI applications.</p><h3>Hello World</h3><p>Let’s use Gitpod to write <a href="https://github.com/32leaves/gitpod-hello-ui-demo">a simple desktop-native application in Go</a> using <a href="https://github.com/andlabs/libui">libui</a>. First, we create a GitHub repo and a <a href="https://github.com/32leaves/gitpod-hello-ui-demo/commit/fea580735c09fa704531a810e8ec7ca6a5c03a88">little bit of configuration</a>: we need a Dockerfile to install libui’s dependencies (see below), and we need to tell Gitpod to use that Dockerfile.</p><pre>FROM gitpod/workspace-full-vnc<br>RUN apt-get update \<br>    &amp;&amp; apt-get install -y libgtk-3-dev</pre><p>This Dockerfile uses the gitpod/workspace-full-vnc image which sports the setup necessary to run X11 and VNC in Gitpod. It runs a <a href="https://novnc.com/">web-based VNC viewer</a> on port 6080 — during startup, Gitpod will ask you if you want to open this page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8xUjJfd3pV0QXyK-ytyhwA.png" /><figcaption>The Hello World UI example running in Gitpod</figcaption></figure><h3>Native UI in Gitpod = X11 + VNC</h3><p><a href="https://gitpod.io/">Gitpod</a> runs on Linux, so we need an X11 server that our UI application can connect to. As we do not have a physical display attached, we’ll use a framebuffer based X server, namely Xvfb. Using <a href="http://www.karlrunge.com/x11vnc/">x11vnc</a>, we can serve the virtual screen of the X server to a VNC client. There are a few VNC clients that run in the browser out there, but we’ll go with one that’s battle tested: <a href="https://novnc.com/info.html">novnc</a>. The combination of Xvfb, x11vnc and novnc is a proven one, and it happens to be the same that e.g. <a href="https://janitor.technology/">Janitor</a> relies on.</p><p>To make this setup work in Gitpod, we first create a Docker image that has the required tools installed, and a small bash script to tie things together. I went ahead and prepared those things in the <a href="https://github.com/gitpod-io/workspace-images/tree/master/full-vnc">workspace images repo</a>. Any Gitpod workspace started using the workspace-full-vnc image, has a DISPLAY environment variable set in the .bashrc and comes with a running X11 server. No need for any manual setup.</p><h3>Let’s go big: running Visual Studio Code in Gitpod</h3><p>Using this setup, we can build and <a href="https://gitpod.io/#github.com/microsoft/vscode">run Visual Studio Code in Gitpod</a>. VS Code needs a few more libraries than the bare-bones X11 setup we’ve built so far. But again those libraries are easy enough to install in a Dockerfile:</p><pre>FROM gitpod/workspace-full-vnc</pre><pre>RUN apt-get update \<br> &amp;&amp; apt-get install -y libx11-dev libxkbfile-dev libsecret-1-dev libgconf2–4 libnss3</pre><p>I added this setup to <a href="https://github.com/gitpod-io/definitely-gp/tree/master/vscode">definitely-gp</a>, so that when you open the VS code repository in Gitpod, it will build the application, and start it. To see and interact with the application, open the noVNC session that’s served on port 6080:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-yHSkPGNR6Vs07MjLKQAUA.gif" /></figure><h3>Conclusion</h3><p>By plugging together a handful of tools we can develop native UI applications in Gitpod, and stay in the browser altogether. Naturally, this comes with a few limitations, e.g. at the moment this is Linux only, so testing on different platforms is not feasible. Also, noVNC disconnects from the VNC server every now and then; reloading noVNC brings it back.</p><p>Surprisingly, frame-rate is not one of those limitations: you could <a href="https://gitpod.io/#https://github.com/32leaves/gitpod-browser-demo">open a browser inside a Gitpod</a> and watch YouTube videos; it’s best you pick one without sound, though. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15af2967c24e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/developing-native-ui-applications-in-gitpod-15af2967c24e">Developing native UI applications in Gitpod</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gitpod — October 2018 Release]]></title>
            <link>https://medium.com/gitpod/gitpod-october-2018-release-672c91294b40?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/672c91294b40</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[ide]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Sven Efftinge]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 09:08:38 GMT</pubDate>
            <atom:updated>2018-10-01T11:48:31.356Z</atom:updated>
            <content:encoded><![CDATA[<p>It has been a month already since we went public with <a href="https://medium.com/gitpod/gitpod-gitpod-online-ide-for-github-6296b907a886">Gitpod.io</a>. We want to take a moment and <strong>send out a big thank you for all the great feedback </strong>and kind words! ❤️</p><p>We are working to incorporate all your feedback continuously, adding new features, fixing bugs and improving the overall usability and performance.<br>Please keep sending all that useful feedback!</p><p>Today, we are pleased to announce a new version of <a href="https://www.gitpod.io/">Gitpod</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TrpIB26qJjpdoAmh" /><figcaption>Photo by <a href="https://unsplash.com/@parkstreet?utm_source=medium&amp;utm_medium=referral">Audrey Fretz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Here are the most important new features and improvements:</p><h3>Unlimited Gitpod Hours! 🎁</h3><p>To allow you using Gitpod as much as you want, during the beta you can now <br><strong>add extra Gitpod Hours whenever you run low on them</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUfY6XPR9o74dYU1kNWvcA.png" /></figure><h3>Docker File Support ⚙️</h3><p>Most projects need special tools, which can be provided by naming a custom Docker image in your <em>.gitpod</em> file.</p><p>Starting today, you can point to a <em>Dockerfile</em> that sits next to the <em>.gitpod</em> file. Gitpod will take care of building and caching it for you. Instead of managing your own docker builds and versions, simply put the <em>Dockerfile</em> into the repository and you will always have a working setup for the branch at hand.</p><p>Please read <a href="https://medium.com/gitpod/bring-your-own-docker-image-to-gitpod-52db1aa861de">Gero’s post</a> explaining this feature in more detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBKSgvfSNzbcyz8YUIc4cg.png" /></figure><h3>Introduced CLI ⌨️</h3><p>We have introduced a CLI which allows controlling the IDE from the command line, for instance you can open files. Try:</p><pre>gp open path/to/file</pre><p>or just</p><pre>open path/to/file</pre><p>or in case your muscle memory is taking over :)</p><pre>code path/to/file </pre><p>We will add more features to the CLI. If you have ideas or demands please file tickets <a href="https://github.com/gitpod-io/gitpod/issues">over here</a>.</p><h3>GitHub Bot 🤖</h3><p>The <a href="https://github.com/apps/gitpod-io">Gitpod Bot for Github</a> can automatically add Gitpod-links to issues and pull-requests. For instance, if you want to improve onboarding for new contributors you should configure the bot so it adds links to <strong>good_first_issue</strong> or <strong>help_wanted </strong>tagged issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P6TPpSyXQp6SmmhHyVrmBw.png" /></figure><p>We will shortly write a post dedicated to streamlining the contributor’s experience.</p><h3>User Preferences 🤓</h3><p>Preferences and user preferences now allow for customizing your experience individually or per workspace. The workspace preferences are stored in the git repository, while the user preferences are stored in your account and will be used across all your workspaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0SbAwb4vDj28OVvvQmdflQ.png" /></figure><h3>Change Language Mode 💬</h3><p>Sometimes you want to manually change syntax coloring because e.g. no file extension is present. Clicking on the language name in the status bar now allows to quick pick what language to use for an opened editor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HVSkKl7A0oxt3S0UDshHGw.png" /></figure><h3>Enhanced Dashboard 💄</h3><p>In case you want to work a bit longer on a workspace you can now change its description. Also the workspace id is shown in the dashboard so you can tell apart multiple workspaces for the same context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7xvMmtyT_afIYtj0nX-7Pw.png" /></figure><h3>Other Improvements 🚀</h3><p>There are plenty of other improvements and fixes that didn’t make it to the list. For instance, Go-projects are now automatically set up correctly even without any configuration. Also there are plenty of enhancements that have been added to the <a href="https://github.com/theia-ide/typescript-language-server">TypeScript language server</a>. TSLint now works great and we laid out the foundation to add specific editing support for more frameworks and linters such as Vue.js, Angular and ESLint.</p><p>In addition to the explicitly mentioned features you can find a full list of fixes and changes in the <a href="https://github.com/theia-ide/theia">Theia repository</a>.</p><h3><strong>Next Release 🔆</strong></h3><p>We are targeting a regular release cycle of one month with smaller continuous updates in-between. For the next release we will focus heavily on improving the startup time as well as the lagging dashboards in the US and the Asian region. Besides that we have some exciting new features up our sleeves as well.</p><p>Stay tuned and have fun! 🎉</p><p>(emoji-mode off)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=672c91294b40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/gitpod-october-2018-release-672c91294b40">Gitpod — October 2018 Release</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bring your own (Docker) image to Gitpod]]></title>
            <link>https://medium.com/gitpod/bring-your-own-docker-image-to-gitpod-52db1aa861de?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/52db1aa861de</guid>
            <category><![CDATA[diesel]]></category>
            <category><![CDATA[gitpod]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[rockets]]></category>
            <category><![CDATA[rust]]></category>
            <dc:creator><![CDATA[Gero Posmyk-Leinemann]]></dc:creator>
            <pubDate>Wed, 26 Sep 2018 11:52:15 GMT</pubDate>
            <atom:updated>2018-11-30T12:30:12.478Z</atom:updated>
            <content:encoded><![CDATA[<p>Since we released Gitpod into Public Beta it has been incredibly exciting to see people from all over the world use our service. Even more so with feedback like this:</p><h3>George Kalpakas on Twitter</h3><p>I was playing around with @gitpodio today. It&#39;s almost too good to be true. It&#39;s amazing how far along online IDEs have come.</p><p>Of course, there is always room for improvement, especially with a service as new as Gitpod. Luckily, people have started to share their questions and ideas with us on <a href="https://github.com/gitpod-io/gitpod">https://github.com/gitpod-io/gitpod</a>. One of the most often asked questions was:</p><h4>“How do I add tool XYZ to my workspace?”</h4><p>And indeed that hasn’t been straight forward. You had to:</p><ul><li>create a Dockerfile on your machine</li><li>build that Dockerfile on your machine</li><li>push it to hub.docker.com (no account? Create one first!)</li><li>create a branch in your project with a customized .gitpod.yml file which references that specific image</li><li>visit <em>gitpod.io/#&lt;your-repos-branch-url&gt;</em></li><li>get no feedback except ‘Build has status FAILURE’…</li><li>rinse and repeat from step 2</li></ul><p>That was way too tedious for everyone to start playing around.</p><h4>Let Gitpod do the heavy lifting</h4><p>To improve this experience we introduced<a href="https://github.com/gitpod-io/gitpod/issues/62"> Dockerfile support (#62)</a>, which lets you reference your Dockerfile directly from inside your .gitpod.yml file:</p><pre>image:<br>  file: docker/Dockerfile</pre><p>Now, Gitpod knows about the Dockerfile and builds that image for you. Whenever you access the repository on Gitpod it checks whether the Dockerfile has been updated and rebuilds the image if needed. When this happens you’ll be shown the log output of the build for easier debugging, too.</p><h4>An example, please!</h4><p>Let’s get concrete. As an exercise we’ll use <a href="https://github.com/lankydan/rust-web-with-rocket">a minimal REST service</a> written in<a href="https://www.rust-lang.org/"> Rust</a> using Rocket and Diesel that talks to a PostgreSQL DB. It also has a nice<a href="https://lankydanblog.com/2018/05/20/creating-a-rusty-rocket-fuelled-with-diesel/"> blog post</a> to get started.</p><p>The example relies on a very specific nightly build of the Rust compiler from May 2018. Thus, a simple git clone … &amp;&amp; cargo build &amp;&amp; cargo run won’t get you up-and-running. Of course, you could switch Rust toolchains but then other projects on your machine might stop working. Furthermore, there is more setup and tools to install: A database, a CLI tool…<br>Gitpod to the rescue!</p><p>I went to <a href="https://github.com/gitpod-io/definitely-gp/">gitpod-io/definitely-gp</a> and added a <a href="https://github.com/gitpod-io/definitely-gp/blob/master/rust-web-with-rocket/.gitpod.yml"><em>.</em>gitpod.yml</a> and <a href="https://github.com/gitpod-io/definitely-gp/blob/master/rust-web-with-rocket/Dockerfile">Dockerfile</a> there. The <em>.</em>gitpod.yml file looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/18a3f0e6a78fe28d7e7eb3d77c50d22b/href">https://medium.com/media/18a3f0e6a78fe28d7e7eb3d77c50d22b/href</a></iframe><p>It references the Dockerfile next to it, says that the resulting app should be accessible on port 8000 and contains the command executed on workspace startup: set config, start postgres, build and run app (I basically copied those from the repo’s .md file).</p><p>The Dockerfile itself inherits from our default image <a href="https://hub.docker.com/r/gitpod/workspace-full/">gitpod/workspace-full</a>¹ and contains:</p><ul><li>PostgreSQL (+ some configuration for the gitpod user)</li><li>specific Rust toolchain</li><li>some project specific setup</li></ul><p>Here it is:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/40806efadb1f5b95d21f4d13c934ed99/href">https://medium.com/media/40806efadb1f5b95d21f4d13c934ed99/href</a></iframe><p>Remember, this is done once per project. Most projects already have those setup descriptions, they are just buried inside their README.</p><p>Now whenever anyone accesses the repository through Gitpod, be it a branch, a particular commit, an issue or a<a href="https://medium.com/gitpod/when-code-reviews-lgtm-2fd4ffd66f87"> PR,</a> they will get a custom workspace with all the tools set up and running, out of the box. <a href="http://gitpod.io/#https://github.com/lankydan/rust-web-with-rocket">Give it a spin</a>!</p><p>Once the service has build and is running, we just follow the tutorial:</p><ul><li>Open /people: Click Open on the appearing messagebox² and change the path in the integrated browser to http://8000-&lt;your-workspace-url&gt;/people , click Reload : The query results in an empty []</li><li>Hit F1 -&gt; &quot;Open new Terminal&quot; and paste:</li></ul><pre>curl -XPOST <a href="http://localhost:8000/people">http://localhost:8000/people</a> -H &quot;Content-Type: application/json&quot; --data &#39;{&quot;id&quot;: 123, &quot;first_name&quot;: &quot;Jon&quot;, &quot;last_name&quot;: &quot;Doe&quot;, &quot;age&quot;: 64, &quot;profession&quot;: &quot;Engineer&quot;, &quot;salary&quot;: 1024}&#39;</pre><ul><li>Hit Reload again to see Jon Doe’s people entry</li></ul><h3>Try it yourself</h3><p>You can either create a PR on<a href="https://github.com/gitpod-io/definitely-gp"> gitpod-io/definitely-gp</a> — or dive right in and create the <a href="http://docs.gitpod.io/40_Configuration.html#checked-in-gitpod-file">.gitpod.yml in your repositories</a>! For details on how this works and what is possible please head over to<a href="http://docs.gitpod.io/40_Configuration.html#gitpod-file"> the docs</a>.</p><p>¹ It is not required to inherit from that image at all. You can even start with a plain alpine or debian based image. I used it here for convenience.</p><p>² Alternatively, go to View -&gt; Ports and click Open</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52db1aa861de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/bring-your-own-docker-image-to-gitpod-52db1aa861de">Bring your own (Docker) image to Gitpod</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing a Nuxt.js app entirely in your browser]]></title>
            <link>https://medium.com/gitpod/developing-a-nuxt-js-app-entirely-in-your-browser-94e7525f5eca?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/94e7525f5eca</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[nuxt]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <dc:creator><![CDATA[Sven Efftinge]]></dc:creator>
            <pubDate>Fri, 21 Sep 2018 13:55:15 GMT</pubDate>
            <atom:updated>2018-09-21T14:56:00.977Z</atom:updated>
            <content:encoded><![CDATA[<p>A walkthrough to create a fully working Nuxt.js web application with only a browser, using Gitpod.io the online IDE for GitHub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YlpGv4nlbQP5sEPr" /><figcaption>“person holding lighted sparklers” by <a href="https://unsplash.com/@cristian1?utm_source=medium&amp;utm_medium=referral">Cristian Escobar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Version 2.0 of <a href="https://medium.com/@nuxt_js/nuxt-js-2-0-webpack-4-esm-modules-create-nuxt-app-and-more-6936ce80d94c">Nuxt.js has just been released</a>. It comes with a convenient scaffolding tool that let’s you get started in no time. In the following I will explain the steps necessary to create, run and <strong>develop a Nuxt.js application with only a browser using Gitpod.io</strong>.</p><h3><strong>Step 1: Go to GitHub and create a fresh repository.</strong></h3><p><a href="http://gitpod.io/">Gitpod.io</a> uses GitHub as its dashboard. That means you start your workspaces from any states of any GitHub project. So new projects are created through GitHub, too:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I9sury8siGTS6GtF" /></figure><p>Clicking anywhere on Github’s Octocat logo on the top left will bring you to your dashboard, where you can create a new repository.</p><p>Enter any name description, you can later change it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bY21cCYdJYoj7B48" /></figure><h3><strong>Step 2: Start a Gitpod workspace</strong></h3><p>From your newly created but still empty project you can now start a Gitpod workspace. To do so prefix the GitHub URL with <strong>gitpod.io#</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NjvEmIjiTVwbTIaA" /></figure><h3><strong>Step 3: Run `yarn create nuxt-app`.</strong></h3><p>Now a workspace with an online IDE is started for you. It will open up the readme (if you have created one) and a terminal.</p><p>Using the terminal you can use create-nuxt-app to create an initial project:</p><pre><strong>yarn create nuxt-app</strong></pre><p>Now simply answer all the prompts as you want.</p><h3><strong>Step 4: Allow external access to the dev server</strong></h3><p>By default the dev server doesn’t allow external IPs. To change that so we can access the application running in our cloud container, we need to pass an additional argument to the dev command.</p><p>To do so open the package.json file and add the parameter</p><pre><strong>—-hostname 0.0.0.0</strong></pre><p>as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WrSSKAEkumvfIv6d" /></figure><h3>Step 5: Start the dev server</h3><p>Now we can start the dev server and see the application in action.</p><p>In the terminal type</p><pre><strong>yarn dev</strong></pre><p>A notification window will pop up asking you to either open the web app externally or in a view side-by-side to the editor area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*psT2Ar8PKkWYVpKV" /><figcaption>Running app in the Gitpod workspace</figcaption></figure><h3><strong>Bonus Points</strong></h3><p>Now you can start changing the application and of course committing to your repo. Also you should consider adding a <em>.gitpod</em> file to the root directory, so the build and dev server automatically startup next time you open a Gitpod workspace.</p><p>Here’s the contents:</p><pre>ports:<br>  - port: 3000<br>    protocol: &quot;http&quot;<br>tasks:<br>  - command: &gt;<br>        yarn install &amp;&amp;<br>        yarn dev</pre><h3>Dive deeper into Nuxt.js</h3><p>Now you are all set to dive a bit deeper into Nuxt.js. Checkout the <a href="https://github.com/nuxt-community/awesome-nuxt">awesome-nuxt</a> repository or the <a href="https://nuxtjs.org/">website</a> for further tips and tutorials.</p><p>Have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94e7525f5eca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/developing-a-nuxt-js-app-entirely-in-your-browser-94e7525f5eca">Developing a Nuxt.js app entirely in your browser</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gitpod — Online IDE For GitHub]]></title>
            <link>https://medium.com/gitpod/gitpod-gitpod-online-ide-for-github-6296b907a886?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/6296b907a886</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[ide]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Sven Efftinge]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 16:09:17 GMT</pubDate>
            <atom:updated>2018-11-16T14:13:51.493Z</atom:updated>
            <content:encoded><![CDATA[<p>After over one year of intensive work, we are proud to announce the public Beta of <a href="http://gitpod.io/">Gitpod</a>.</p><p>Gitpod is an online IDE which can be launched from any GitHub page. Simply <strong>prefix any GitHub-URL with “<em>https://gitpod.io#”</em></strong> or use our <a href="https://chrome.google.com/webstore/detail/gitpod-online-ide/dodmmooeoklaejobgleioelladacbeki?hl=en">browser extension</a> that adds a button to GitHub pages.</p><p>Within seconds, Gitpod provides you with a fully working development environment, including a VS Code-powered IDE and a cloud-based Linux container configured specifically for the project at hand.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FD41zSHJthZI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DD41zSHJthZI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FD41zSHJthZI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d16ef9cb031d5884719a7028d6137c98/href">https://medium.com/media/d16ef9cb031d5884719a7028d6137c98/href</a></iframe><h3><strong>Yet Another Cloud IDE?</strong></h3><p>Gitpod is not another cloud IDE, aiming at replacing desktop development. Instead, Gitpod is a natural extension to GitHub. The limited editing capabilities of GitHub are far too often forcing context switches to our local machines. <strong>Gitpod extends our life on GitHub</strong>.</p><p>Also, Gitpod is super simple: You don’t maintain your projects or workspaces using overwhelming and complicated dashboards. Instead, any configuration is safely stored and versioned on GitHub.</p><h3><strong>Stay In The GitHub Flow</strong></h3><p>Gitpod is highly contextual, such that it opens the IDE in the correct mode depending on the context:</p><p>If you are looking at a particular file of a certain commit on GitHub, starting a Gitpod workspace will check out the right version and open the file you’ve been looking at in the IDE.</p><p>Starting a Gitpod workspace from an issue will automatically create a branch and preconfigure the commit message.</p><p><strong>Starting Gitpod from a pull request beams your right into code review mode.</strong></p><h3><strong>GitHub Integration</strong></h3><p>Once you are in the IDE, you can interact with GitHub in various ways. Besides the obvious Git integration, you can do things like <strong>commenting inline in editors, approving and even merging PRs</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNDYawJpDgX6gP_e0w17mg.png" /><figcaption>Inline Comments For Pull Requests</figcaption></figure><h3><strong>Automated Setup</strong></h3><p>Gitpod is built on Kubernetes and you can use any Docker image for your development environments. This allows to fully automate the setup and frees everybody from manually going through long and outdated setup documentation. No more “works on my machine” scenarios.</p><p>Gitpod provides your collaborators a <strong>single-click-to-contribute</strong> <strong>experience</strong>.</p><p>More information on how to configure Gitpod can be found <a href="http://docs.gitpod.io/40_Configuration.html">here</a>.</p><h3><strong>Fire and Forget</strong></h3><p>Gitpod workspaces are disposable. You simply create a fresh one whenever you need. Once you are done with your task, the IDE brings you back to GitHub, so you can continue on the next task.</p><p>You usually never need to go back to any workspace, but of course you can in case you need to.</p><h3><strong>Full Terminal Access</strong></h3><p>Gitpod gives developers full featured terminals to run any processes such as compiling, linting or simply running tests or your application. Any docker image works and you can even configure Gitpod to automatically launch certain tasks on start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8oKjiVfaptpeI27UXPbcA.png" /></figure><h3><strong>Open Source</strong></h3><p>The IDE in Gitpod is based on <a href="http://theia-ide.org/">Theia</a>, an open-source project that we (<a href="http://typefox.io/">TypeFox</a>) have started together with our friends from Ericsson in early 2017. You can think of it as <strong>the online version of VS Code</strong>. We love VS Code, but needed some additional properties, like a more extensible architecture and the ability to run in browsers connected to a remote backend. Theia is a true open-source project, hosted at the Eclipse Foundation and developed by a diverse crowd of engineers backed by TypeFox, Ericsson, Red Hat, Arm and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5DnbR6-FbyVQ8ILgFHJXOw.png" /><figcaption>Language Tooling In Action</figcaption></figure><h3><strong>Supports Many Languages</strong></h3><p>Being based on VS Code and its Language Server Protocol, Theia supports most major programming languages. The table below provides a good overview of the current state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BshL6_wwY2XYRDKSMYiSDg.png" /><figcaption>Current State of Supported Programming Languages</figcaption></figure><p>Additional languages like <strong>C#, Swift, Clojure, Groovy, Objective-C, Markdown, Less, XML and many others</strong> are supported with syntax coloring, as well. Because it is so easy to create an extension for Theia, support will improve both in breadth (more languages) and depth, shortly.</p><h3><strong>Use It For Free!</strong></h3><p>You can use Gitpod with any GitHub repository. The login is done through GitHub OAuth. At first, Gitpod will ask for accessing public repos, only. If you want to use it with a private repository, Gitpod will ask again for more permissions.</p><p>Why not try it now? If you don’t have a particular repository in mind, you can pick one of the below:</p><ul><li><strong>JavaScript</strong>:<br><a href="https://gitpod.io/#https://github.com/ooade/NextSimpleStarter">https://gitpod.io#<strong>https://github.com/ooade/NextSimpleStarter</strong></a></li><li><strong>Go</strong>:<br><a href="https://gitpod.io/#https://github.com/demo-apps/go-gin-app">https://gitpod.io#<strong>https://github.com/demo-apps/go-gin-app</strong></a></li><li><strong>Java</strong>:<br><a href="https://gitpod.io/#https://github.com/spring-guides/gs-spring-boot">https://gitpod.io#<strong>https://github.com/spring-guides/gs-spring-boot</strong></a></li><li><strong>Ruby</strong>:<br><a href="https://gitpod.io/#https://github.com/gitpod-io/rails_sample_app">https://gitpod.io#<strong>https://github.com/gitpod-io/rails_sample_app</strong></a></li><li><strong>Python</strong>:<br><a href="https://gitpod.io/#https://github.com/sibtc/django-beginners-guide">https://gitpod.io#<strong>https://github.com/sibtc/django-beginners-guide</strong></a></li><li><strong>PHP</strong>:<br><a href="https://gitpod.io/#https://github.com/symfony/demo">https://gitpod.io#<strong>https://github.com/symfony/demo</strong></a></li></ul><h3><strong>Where Are We Going From Here?</strong></h3><p>Many other features are ready to use, such as Git integration or the search functionality. But also exciting new features are in development, such as <strong>debugging, collaboration </strong>and <strong>support for GitLab and Bitbucket</strong>. Even <strong>support for VS Code extensions</strong> is on its way.</p><p>Besides more features, we are focussing on improving the overall experience by streamlining rough edges, fixing bugs and improving performance. New releases will come out continuously.</p><p>If you have feedback or find bugs, please <a href="https://github.com/gitpod-io/gitpod/issues">file them here</a>.</p><p><strong>Happy coding!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6296b907a886" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/gitpod-gitpod-online-ide-for-github-6296b907a886">Gitpod — Online IDE For GitHub</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Better GitHub Flow]]></title>
            <link>https://medium.com/gitpod/github-flows-better-with-gitpod-e455d17990f9?source=rss----f9406e1af61f---4</link>
            <guid isPermaLink="false">https://medium.com/p/e455d17990f9</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[online-ide]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Sven Efftinge]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 13:01:01 GMT</pubDate>
            <atom:updated>2018-08-20T12:52:08.537Z</atom:updated>
            <content:encoded><![CDATA[<p>As software developers, we already spend a lot of our time in browsers. Be it for searching Google/StackOverflow, checking our latest Continuous Integration builds on Jenkins resp. Travis, or doing code reviews on GitHub, Bitbucket, or Gerrit. Also, communication with the team happens in web applications, such as Gmail, Google Hangout or Slack. The convenience of web applications and OAuth-based authentication allows us to use any computer to do most of our work immediately.</p><p>However, when it comes to the actual coding and debugging, we have to prepare our local development environments manually. We do this based on often outdated, incomplete or just plain wrong documentation. The transition from an online repository to the actual coding is a barrier that hinders thousands of possible contributions every day. Coding needs to get more accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f260tcqJvgvCguFu" /><figcaption>(Source: <a href="http://dilbert.com/strip/2017-01-02)">http://dilbert.com/strip/2017-01-02)</a></figcaption></figure><p>But that only needs to be done once, right? Unfortunately, no. Coding is a team sport. We are not just adding code, but also do code reviews or fix bugs on maintenance branches which often require a different setup. Moreover, today’s applications are loosely coupled compositions of independent microservices and sub-projects, written in different languages requiring different development setups. Consequently, we have to maintain setups for multiple projects and branches, trying to keep documentation in sync including all the cases for the different platforms. As a result, we are wasting precious time every day. We should spend this time and effort on more fun and productive things.</p><p>Once we have the setup, we run builds and test suites. Those processes are usually an excellent reason to grab a coffee because it is blocking our machine. Wouldn’t it be nice to push such workload to the cloud, where it not only runs faster but can easily be parallelized? Your computer stays calm and cool, and you still can have your coffee if you want.</p><p>In this article, I will walk you through an automated, cloud-based development workflow. <a href="https://gitpod.io/">Gitpod</a> is based on Kubernetes, GitHub, and the new Eclipse Theia project — a VS Code-like IDE that runs in modern browsers. You can think of it as an online IDE with deep GitHub integration (and soon other platforms), providing fully-featured development environments with a single click for any GitHub project, issue, branch or pull request.</p><p><strong>Automation</strong></p><p>Starting a workspace with Gitpod is much easier than with other cloud IDEs. Gitpod doesn’t require you to configure workspaces with container images, Git information and so on. Instead, you directly go to a GitHub repository and click the Gitpod-Button [see below]. Gitpod provides you with a ready to use workspace, so that you can immediately start coding without any configuration steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MjUIJ1zspz3CF8oo" /><figcaption>Button provided by Gitpod’s browser extension</figcaption></figure><blockquote>To see the Gitpod button on the GitHub page, you would have to <a href="https://gitpod.io/">install a browser extension</a>. Alternatively, you can manually prefix any GitHub URL with `https://gitpod.io#`. For instance, clicking the following link will instantly provide you a development workspace for the Eclipse Theia project: <a href="https://gitpod.io/#https://github.com/theia-ide/theia">https://gitpod.io#https://github.com/theia-ide/theia</a></blockquote><p>Of course, different projects need different setups. Gitpod has a three-stage process to determine the workspace configuration, e.g. what docker image to use for development, what startup script to run, and which ports to expose:</p><ol><li>It first looks for a <em>.gitpod</em> configuration file in the repository. Note, that it will check the state of the currently viewed commit. This allows you to keep working configuration for old states as well as trying a new configuration in a pull request.</li><li>Second, if there is no configuration in the cloned repository, a central repository called ‘<a href="https://github.com/gitpod-io/definitely-gp">definitely-gp</a>’ is checked for configuration. It is a public repository which contains configurations for arbitrary GitHub projects. That is useful if you want to provide configuration for a repository you don’t have write access to. Everybody is invited to contribute to this.</li><li>As a last resort, Gitpod analyzes the repository and derives a suitable configuration from there. For instance, if the repository contains a `yarn.lock` file it will automatically run `yarn install` in the beginning.</li></ol><p>The key takeaway here is that you can handcraft a Docker file that includes all the development tools you need for your project as well as any ports to be exposed or scripts you want to run when a workspace starts. You can put that configuration under version control, replacing the onboarding documentation with a formal, executable description. But there is more information in a GitHub URL that can be leveraged to keep us in the flow.</p><p><strong>It’s All About The Context</strong></p><p>When creating a workspace, Gitpod will analyze the provided GitHub URL. If you are looking at a particular branch it will check out that branch; if you are looking at a specific file, it will automatically open that file in Gitpod’s IDE.</p><p>Some great features, which are heavily used on GitHub, are issues and pull requests. If you want to start working on a GitHub issue, you simply spawn a fresh workspace from the issue page on GitHub. Gitpod puts you into the right context, by automatically creating a local branch using the issue number and even pre-configures the commit message accordingly. All is set up for you to start coding and testing. Once you are happy with the changes you made, use the Git integration to create a commit and push it to a remote branch. Finally, you can even create the actual pull request right from within Gitpod.</p><p>Lastly, of course, when clicking the Gitpod button on a pull request, Gitpod beams you right into the code review mode. A panel on the left will list the changed files, allowing you to go through them one by one. Changes are opened in the diff editor where you can also read and add review comments. And because it is a full IDE, we can navigate through the entire code base, run code or add commits at will. Approving the pull request is supported, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8N39dT5P6Q1zQdIR" /><figcaption>Inline code review comments</figcaption></figure><p><strong>Theia IDE</strong></p><p>All the smart automation doesn’t help if you end up with a bad development experience. So let’s talk about the IDE that powers Gitpod.</p><p>Theia is an open-source project that has been in development for over a year now. In addition to the TypeFox team, other companies like Ericsson and RedHat are actively contributing to it. The Eclipse Che team is replacing their existing IDE with Theia, and companies like IBM already have <a href="https://microclimate-dev2ops.github.io/">public offers</a> based on it. Theia just recently became an Eclipse project, to make sure it is developed in a truly open and democratic manner and that no single company is controlling its future.</p><p>Even with all that momentum, it seems to be an unrealistic effort to develop a new IDE from scratch. Just consider how many years of development were put into projects like the classic Eclipse IDE or Visual Studio. Gladly, this is not what the Theia team is doing.</p><p>The most important building blocks for Theia are probably the Monaco editor and the use of protocols. Monaco is the code editor that supports VS Code and is very flexible, high-quality code editor written in TypeScript (JavaScript). Unlike VS Code, the Monaco editor widget can run in browsers.</p><p>The second ingredient is the use of protocols. The most popular one being the language server protocol [4].</p><p><strong>The </strong><a href="https://microsoft.github.io/language-server-protocol/"><strong>Language Server Protocol (LSP)</strong></a></p><p>The LSP is an effort started by VS Code to allow using language services in a technology- and UI-independent manner. One of the first popular reusable language services came from the TypeScript team. Such a service is a simple headless process that provides language smartness to an editor / IDE through messaging.</p><p>For instance, a text editor, supporting the LSP, can ask a language server for completion proposals given a document and a cursor position. All the heavy lifting such as parsing, type resolution, and linting is done in the language server. The IDE only needs to know how to represent the returned information for the user, e.g. propose the completion proposals in a pop-up.</p><p>As of May 2018, there are 64 language servers listed on the <a href="https://microsoft.github.io/language-server-protocol/implementors/servers/">official site</a> covering all of the mainstream programming languages, such as JavaScript, Python, Java, C++ or Go. If something is missing, it is a good idea to search the web as the list is incomplete and new language servers are released every other week. If you want to build your own language server, there are SDKs for various languages ranging from TypeScript, Java and C# to Haskell. Finally, <a href="https://github.com/theia-ide/theia-xtext">Xtext</a> provides a full framework for implementing a language server for domain-specific languages.</p><p>The LSP allows moving mature code bases for language smartness to the future. The very popular Java language server which is not only used in Theia but also in Atom and VS Code is really a headless version of Eclipse’s Java Development tools.</p><p>Theia uses and supports other protocols as well. For instance, debugging support is in the works and will support the Debug Adapter Protocol which connects Theia to 50+ existing debuggers.</p><p><strong>Extensibility</strong></p><p>Besides the ability to run Theia in browsers there is another important difference to VS Code: VS Code extensions are limited to what is exposed in the VS Code’s extension API. For instance, it is not possible to create a new view in a VS code extension. This is a serious blocker for more advanced extensions. Contrarily in Theia where extensions are first class building blocks an extension can deep integration and make use of everything. Even fully white-labeled products are possible due to its flexible architecture. That said, the Theia team is working on supporting VS Code extensions, additionally.</p><p><strong>Outlook</strong></p><p>Providing automated and disposable workspaces that tightly integrate with GitHub projects and the different contexts eliminates time-consuming transitions and streamlines the developer experience. No more ‘it works on my machine’ conversations can happen, because everybody uses the very same setup, which matches the production environment. The smooth onboarding experience will not only help professional developers but lower the barrier for contributions on open-source projects and start coding in general.</p><p>Gitpod is currently going through a public beta phase, where it can be used on public repositories. We are working on improved security, better performance and more cool features. Also, Gitpod is getting support for integration with additional applications, such as Bitbucket, Gitlab, and Gerrit.</p><p>Open-source projects like Kubernetes, Theia, TypeScript, VS Code and thousands of other libraries are the giant’s shoulders Gitpod is based on. We hope by offering free usage of Gitpod for public GitHub projects we can further support the flourishing landscape of open-source projects, making it easier for everyone to contribute and for maintainers to review those contributions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e455d17990f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitpod/github-flows-better-with-gitpod-e455d17990f9">A Better GitHub Flow</a> was originally published in <a href="https://medium.com/gitpod">Gitpod</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>