Updates README & guides.

Author: Mike Nikles

README.md

@@ -1,6 +1,6 @@
 # OpenVSCode Server
 
-[![Gitpod ready-to-code](https://img.shields.io/badge/Gitpod-ready--to--code-908a85?logo=gitpod)](https://gitpod.io/from-referrer/)
+[![Gitpod ready-to-code](https://img.shields.io/badge/Gitpod-ready--to--code-908a85?logo=gitpod)](https://github.com/gitpod-io/openvscode-server/) ![GitHub](https://img.shields.io/github/license/gitpod-io/openvscode-server) ![Discord](https://img.shields.io/discord/816244985187008514)
 
 ## What is this?
 
@@ -10,48 +10,67 @@ This project provides a version of VS Code that runs a server on a remote machin
 
 ## Why?
 
-VS Code has traditionally been a desktop IDE built with web technology. A few years back people started patching it, in order to run it in a remote context and to make it accessible through web browsers. These efforts have been complex and error prone, because many changes had to be made across the large code base of VS Code.
+VS Code has traditionally been a desktop IDE built with web technologies. A few years back, people started patching it in order to run it in a remote context and to make it accessible through web browsers. These efforts have been complex and error prone, because many changes had to be made across the large code base of VS Code.
 
-Luckily in 2019 the VS Code team started to refactor its architecture to support a browser-based working mode. While this architecture has been adopted by Gitpod and GitHub, the important bits have not been open-sourced, yet. As a result many people in the community are still using the old hard to maintain and error-prone approach.
+Luckily, in 2019 the VS Code team started to refactor its architecture to support a browser-based working mode. While this architecture has been adopted by Gitpod and GitHub, the important bits have not been open-sourced, until now. As a result, many people in the community still use the old, hard to maintain and error-prone approach.
 
-At Gitpod we've been asked a lot about how we do it. So we thought we might just share the minimal set of changes needed, so people can rely on the latest version of VS Code, have a straightforward upgrade path and low maintenance effort.
+At Gitpod, we've been asked a lot about how we do it. So we thought we might as well share the minimal set of changes needed so people can rely on the latest version of VS Code, have a straightforward upgrade path and low maintenance effort.
 
 ## Getting started
 
 ### Docker
 
 - Start the server:
-```bash
-docker run -it --init -p 3000:3000 -v "$(pwd):/home/workspace:cached" gitpod/openvscode-server
-```
-- after this, visit [localhost:3000](http://localhost:3000).
+	```bash
+	docker run -it --init -p 3000:3000 -v "$(pwd):/home/workspace:cached" gitpod/openvscode-server
+	```
+- Visit [localhost:3000](http://localhost:3000).
 
-You can use `nightly` tag to test nightly changes.
+_Note_: Feel free to use the `nightly` tag to test the latest version, i.e. `gitpod/openvscode-server:nightly`.
 
 ### Linux
 
 - [Download the latest release](https://github.com/gitpod-io/openvscode-server/releases/latest)
-- untar and run the server:
-```bash
-tar -xzf openvscode-server-v${OPENVSCODE_SERVER_VERSION}.tar.gz
-cd openvscode-server-v${OPENVSCODE_SERVER_VERSION}
-./server.sh
-```
-- after this, visit [localhost:3000](http://localhost:3000).
+- Untar and run the server:
+	```bash
+	tar -xzf openvscode-server-v${OPENVSCODE_SERVER_VERSION}.tar.gz
+	cd openvscode-server-v${OPENVSCODE_SERVER_VERSION}
+	./server.sh
+	```
+- Visit [localhost:3000](http://localhost:3000).
 
-You can use [prerelease](https://github.com/gitpod-io/openvscode-server/releases) to test nightly changes.
+_Note_: You can use [pre-releases](https://github.com/gitpod-io/openvscode-server/releases) to test nightly changes.
+
+### Deployment guides
+
+Please refer to [Guides](./docs/guides/README.md) to learn how to deploy OpenVSCode Server to your cloud provider of choice.
 
 ## The scope of this project
 
-This project really only adds the minimal bits required to run VS Code in a server scenario. We have no intention of changing VS Code in any way or adding additional features through this. Feature requests, bug fixes, etc. should go to the upstream repository.
+This project only adds minimal bits required to run VS Code in a server scenario. We have no intention of changing VS Code in any way or to add additional features to VS Code itself. Please report feature requests, bug fixes, etc. in the upstream repository.
 
-> **For any feature requests, bug reports, or contributions that are not specific to running VS Code in a server context,**
->
-> **please go to [Visual Studio Code - Open Source "OSS"](https://github.com/microsoft/vscode)**
+> **For any feature requests, bug reports, or contributions that are not specific to running VS Code in a server context, please go to [Visual Studio Code - Open Source "OSS"](https://github.com/microsoft/vscode)**
 
 ## Supporters
+
 The project is supported by companies such as [GitLab](https://gitlab.com/), [VMware](https://www.vmware.com/), [Uber](https://www.uber.com/), [SAP](https://www.sap.com/), [Sourcegraph](https://sourcegraph.com/), [RStudio](https://www.rstudio.com/), [SUSE Rancher](https://rancher.com/), [Tabnine](https://www.tabnine.com/), [Render](https://render.com/) and [TypeFox](https://www.typefox.io/).
 
 ## Contributing
 
-[See development docs.](./docs/development.md)
+Thanks for your interest in contributing to the project 🙏. You can start a development environment with the following button:
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/gitpod-io/website)
+
+To learn about the code structure and other topics related to contributing, please refer to the [development docs](./docs/development.md).
+
+## Authors
+
+- [Anton Kosyakov](https://www.github.com/akosyakov)
+- [Jean Pierre Huaroto](https://www.github.com/jeanp413)
+- [Filip Troníček](https://www.github.com/filiptronicek)
+
+## Community & Feedback
+
+To learn what others are up to and to provide feedback, please head over to the [Discussions](https://github.com/gitpod-io/openvscode-server/discussions).
+
+You can also follow us on Twitter [@gitpod](https://twitter.com/gitpod) or come [chat with us](https://www.gitpod.io/chat).

docs/guides/README.md

@@ -6,7 +6,7 @@ Each directory contains a `README.md` file as the main guide. Additional, suppor
 
 ## Add a new guide
 
-We welcome community contributions 🙏. Please open an issue and/or pull request if you would like to add new deployment guides.
+We welcome community contributions 🙏. Please open an issue and/or pull request if you would like to add a new deployment guide.
 
 To add a new guide:
 1. Copy the `_template` directory and name it based on the deployment platform you write a guide for

docs/guides/aws-ec2/README.md

@@ -0,0 +1,65 @@
+# Deploy OpenVSCode Server to AWS EC2
+
+## Prerequisites
+
+To complete this guide, you need:
+* an [AWS](https://aws.amazon.com/) account
+
+## Setup
+
+### Create a VM
+
+1. Navigate to https://console.aws.amazon.com/ec2
+1. Launch a Ubuntu 20.04 instance with the default settings
+  * **Caution**: Please follow security best practices when setting up your VM
+
+### Download & extract OpenVSCode Server
+
+**Caution**: Make sure you successfully connected to the VM before you execute the following commands.
+
+First, let's define the release version we want to download. You can find the latest version on the [Releases](https://github.com/gitpod-io/openvscode-server/releases) page.
+
+```bash
+export SERVER_VERSION=1.60.0 # Replace with the latest version
+```
+
+With that in place, let's download & extract OpenVSCode server:
+
+```bash
+wget https://github.com/gitpod-io/openvscode-server/releases/download/openvscode-server-v$SERVER_VERSION/openvscode-server-v$SERVER_VERSION-linux-x64.tar.gz -O code-server.tar.gz
+tar -xzf code-server.tar.gz
+rm code-server.tar.gz
+```
+
+### Create an inbound rule for port 3000
+
+To access OpenVSCode Server on port 3000 later, we have to create an inbound rule:
+1. Open the instance summary page
+1. Select the "Security" tab
+1. In the "Security groups" section, click on the link to open the security group page
+1. In the "Inbound rules" table, click the "Edit inbound rules" button on the right side
+1. Click "Add rule" and populate the following fields (use default values for everything else):
+  * Type: Custom TCP
+	* Port range: 3000
+	* Source: Anywhere-IPv4
+1. Click "Save rules"
+
+## Start the server
+
+While you are still connected to the VM, execute the following commands to start OpenVSCode Server:
+
+```bash
+cd openvscode-server-v$SERVER_VERSION-linux-x64
+./server.sh
+```
+
+## Access OpenVSCode Server
+
+1. Navigate to your VM's instance summary page
+1. Copy the "Public IPv4 address"
+1. Paste the IP address in a new browser tab and add `:3000`, i.e. `http://18.118.194.234:3000`
+
+## Teardown
+
+1. Navigate to your VM's instance summary page
+1. Click "Instance state" and select "Terminate instance"