2019-03-04 19:31:27 +01:00
|
|
|
# Getting Started
|
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
[code-server](https://coder.com) is used by developers at Azure, Google,
|
|
|
|
Reddit, and more to give them access to VS Code in the browser.
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-03-21 15:39:34 +01:00
|
|
|
## Quickstart Guide
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
> NOTE: If you get stuck or need help, [file an issue](https://github.com/cdr/code-server/issues/new?&title=Improve+self-hosted+quickstart+guide),
|
|
|
|
> [tweet (@coderhq)](https://twitter.com/coderhq) or
|
|
|
|
> [email](mailto:support@coder.com?subject=Self-hosted%20quickstart%20guide).
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
This document pertains to Coder-specific implementations of VS Code. For
|
|
|
|
documentation on how to use VS Code itself, please refer to the official
|
|
|
|
[documentation for VS Code](https://code.visualstudio.com/docs)
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
It takes just a few minutes to get your own self-hosted server running. If
|
|
|
|
you've got a machine running macOS, Windows, or Linux, you're ready to start
|
|
|
|
the binary which listens on ports `8443` and `8444` by default.
|
2019-03-04 19:31:27 +01:00
|
|
|
|
|
|
|
<!--
|
|
|
|
DO NOT CHANGE THIS TO A CODEBLOCK.
|
|
|
|
We want line breaks for readability, but backslashes to escape them do not work cross-platform.
|
|
|
|
This uses line breaks that are rendered but not copy-pasted to the clipboard.
|
|
|
|
-->
|
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
1. Visit [the releases](https://github.com/cdr/code-server/releases) page and
|
|
|
|
download the latest cli for your operating system.
|
|
|
|
2. Double click the executable to run in the current directory.
|
|
|
|
3. Copy the password that appears in the CLI. <img src="../assets/cli.png">
|
|
|
|
4. In your browser navigate to `localhost:8443`.
|
|
|
|
5. Paste the password from the cli into the login window. <img src="../assets/server-password-modal.png">
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
> NOTE: Be careful with your password as sharing it will grant those users
|
|
|
|
> access to your server's file system
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-03-21 15:39:34 +01:00
|
|
|
### Things To Know
|
2019-07-16 21:57:02 +02:00
|
|
|
- When you visit the IP for your code-server instance, you will be greeted with
|
|
|
|
a page similar to the following screenshot. Code-server is using a
|
|
|
|
self-signed SSL certificate for easy setup. In Chrome/Chromium, click
|
|
|
|
**"Advanced"** then click **"proceed anyway"**. In Firefox, click
|
|
|
|
**Advanced**, then **Add Exception**, then finally **Confirm Security
|
|
|
|
Exception**. <img src ="../assets/chrome_warning.png">
|
2019-03-04 19:31:27 +01:00
|
|
|
|
|
|
|
## Usage
|
2019-07-16 21:57:02 +02:00
|
|
|
```
|
|
|
|
code-server --help
|
|
|
|
```
|
|
|
|
|
|
|
|
code-server can be ran with a number of arguments to customize your working
|
|
|
|
directory, host, port, and SSL certificate.
|
|
|
|
|
|
|
|
### Data Directory
|
|
|
|
Use `code-server --user-data-dir path/to/directory` to specify the root folder
|
|
|
|
that VS Code will start in.
|
|
|
|
|
|
|
|
### Host
|
|
|
|
By default, code-server will use `127.0.0.1` for insecure connections and
|
|
|
|
`0.0.0.0` for secure connections. This can be changed by using
|
|
|
|
`code-server --host `.
|
|
|
|
|
|
|
|
> Example: `code-server --host 127.0.0.1`
|
|
|
|
|
|
|
|
### Open
|
|
|
|
You can have the server automatically open the VS Code in your browser on
|
|
|
|
startup by using the `code-server -o` or `code-server --open` flags
|
|
|
|
|
|
|
|
### Port
|
|
|
|
By default, code-server will use `8443` as its port. This can be changed by
|
|
|
|
using `code-server -p` or `code-server --port=` followed by the port you want
|
|
|
|
to use.
|
|
|
|
|
|
|
|
> Example: `code-server -p 9000`
|
|
|
|
|
|
|
|
### Cert and Cert Key
|
|
|
|
To encrypt the traffic between the browser and server use `code-server --cert`
|
|
|
|
followed by the path to your `.cer` file. Additionally, you can use certificate
|
|
|
|
keys with `code-server --cert-key` followed by the path to your `.key` file.
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
Example:
|
|
|
|
```
|
|
|
|
code-server --cert /path/to/certificate/fullchain.cer --cert-key /path/to/certificate/fullchain.key
|
|
|
|
```
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
Example for Let's Encrypt:
|
2019-03-04 19:31:27 +01:00
|
|
|
```
|
2019-07-16 21:57:02 +02:00
|
|
|
code-server --cert /etc/letsencrypt/live/example.com/fullchain.pem --cert-key /etc/letsencrypt/live/example.com/privkey.key
|
2019-07-07 09:03:47 +02:00
|
|
|
```
|
2019-03-04 19:31:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
To ensure the connection between you and your server is encrypted view our
|
|
|
|
guide on [securing your setup](../security/ssl.md).
|
|
|
|
|
|
|
|
### Nginx Reverse Proxy
|
|
|
|
Below is a virtual host example that works with code-server. Please also pass
|
|
|
|
`--allow-http` and `--trust-proxy` to code-server to allow the proxy to
|
|
|
|
connect. You can also use Let's Encrypt to get a SSL certificates for free.
|
|
|
|
|
|
|
|
```
|
|
|
|
server {
|
|
|
|
listen 80;
|
|
|
|
listen [::]:80;
|
|
|
|
server_name code.example.com code.example.org;
|
|
|
|
location / {
|
|
|
|
proxy_pass http://localhost:8443/;
|
|
|
|
proxy_set_header Upgrade $http_upgrade;
|
|
|
|
proxy_set_header Connection upgrade;
|
|
|
|
proxy_set_header Accept-Encoding gzip;
|
2019-07-11 04:30:42 +02:00
|
|
|
}
|
2019-07-16 21:57:02 +02:00
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
### Apache Reverse Proxy
|
|
|
|
Example of an HTTPS virtualhost configuration for Apache as a reverse proxy.
|
|
|
|
Please also pass `--allow-http` and `--trust-proxy` to code-server to allow the
|
|
|
|
proxy to connect. You can also use Let's Encrypt to get a SSL certificates for
|
|
|
|
free.
|
2019-06-07 21:22:33 +02:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
```
|
|
|
|
<VirtualHost *:80>
|
|
|
|
ServerName code.example.com
|
2019-03-21 19:49:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
RewriteEngine On
|
|
|
|
RewriteCond %{HTTP:Upgrade} =websocket [NC]
|
|
|
|
RewriteRule /(.*) ws://localhost:8443/$1 [P,L]
|
|
|
|
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
|
|
|
|
RewriteRule /(.*) http://localhost:8443/$1 [P,L]
|
2019-06-07 21:22:33 +02:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
ProxyRequests off
|
2019-03-21 19:49:27 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
RequestHeader set X-Forwarded-Proto https
|
|
|
|
RequestHeader set X-Forwarded-Port 443
|
2019-03-09 20:17:21 +01:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
ProxyPass / http://localhost:8443/ nocanon
|
|
|
|
ProxyPassReverse / http://localhost:8443/
|
|
|
|
|
|
|
|
</VirtualHost>
|
|
|
|
```
|
|
|
|
*Important:* For more details about Apache reverse proxy configuration checkout
|
|
|
|
the [documentation](https://httpd.apache.org/docs/current/mod/mod_proxy.html) -
|
|
|
|
especially the [Securing your Server](https://httpd.apache.org/docs/current/mod/mod_proxy.html#access)
|
|
|
|
section.
|
2019-03-21 19:49:27 +01:00
|
|
|
|
2019-06-07 21:22:33 +02:00
|
|
|
|
2019-07-16 21:57:02 +02:00
|
|
|
### Help
|
|
|
|
Use `code-server --help` to view the usage for the CLI.
|