Go to file
Asher f746212d80
Revamp debugging section (#3224)
- Most people leave the logs out so add a section for them in the issue
  template.
- Remove the VS Code logs because those get sent to stdout now and will
  show up in our logs.
- Separate browser console and network.
2021-04-26 12:56:12 -05:00
.github Revamp debugging section (#3224) 2021-04-26 12:56:12 -05:00
.tours refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
ci chore(ci): migrate from hub to gh (#3168) 2021-04-20 02:21:33 +05:30
docs Revamp debugging section (#3224) 2021-04-26 12:56:12 -05:00
lib/vscode chore(lib/vscode): update netmask (#3187) 2021-04-22 02:57:35 +05:30
src refactor: remove null check in register.ts options.base 2021-04-23 17:09:03 -07:00
test refactor: remove null check in register.ts options.base 2021-04-23 17:09:03 -07:00
typings Fix tsc watch restarting when it shouldn't 2021-04-01 10:58:56 -05:00
.dockerignore Simplify packaging and improve scripts 2020-05-08 01:04:24 -04:00
.editorconfig Add back .editorconfig 2020-02-19 14:22:14 -05:00
.eslintrc.yaml refactor: check for editor consistently in tests 2021-04-06 15:46:58 -07:00
.gitattributes browser: Add favicon.afdesign 2021-01-08 23:03:34 -05:00
.gitignore fix: update path for e2e videos 2021-04-15 11:46:45 -07:00
.prettierrc.yaml Shake CI and docs up 2020-02-14 19:46:17 -05:00
.stylelintrc.yaml Fix bugs in CI 2020-02-18 19:06:35 -05:00
install.sh chore(release): bump version to 3.9.3 2021-04-08 11:18:56 -07:00
LICENSE.txt Shake CI and docs up 2020-02-14 19:46:17 -05:00
package.json feat: add coverage script using codecov 2021-04-22 15:27:54 -07:00
README.md Squashed 'lib/vscode/' changes from fd6f3bce670..ead2c2ab0f5 2021-04-09 11:32:26 +05:30
ThirdPartyNotices.txt Squashed 'lib/vscode/' changes from fd6f3bce670..ead2c2ab0f5 2021-04-09 11:32:26 +05:30
tsconfig.json chore: update ts config and jest config 2021-01-25 16:34:32 -07:00
yarn.lock chore(deps-dev): bump stylelint from 13.12.0 to 13.13.0 (#3218) 2021-04-26 18:03:26 +05:30

code-server · "GitHub Discussions" "Join us on Slack" Twitter Follow

Lines See latest docs

Run VS Code on any machine anywhere and access it in the browser.

Screenshot

Highlights

  • Code on any device with a consistent development environment
  • Use cloud servers to speed up tests, compilations, downloads, and more
  • Preserve battery life when you're on the go; all intensive tasks run on your server

Requirements

For a good experience, we recommend at least:

  • 1 GB of RAM
  • 2 cores

You can use whatever linux distribution floats your boat but in our guide we assume Debian on Google Cloud.

Getting Started

There are three ways you can get started:

  1. Using the install script, which automates most of the process. The script uses the system package manager (if possible)
  2. Manually installing code-server; see Installation for instructions applicable to most use cases
  3. Use our one-click buttons and guides to deploy code-server to a popular cloud provider

If you choose to use the install script, you can preview what occurs during the install process:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run

To install, run:

curl -fsSL https://code-server.dev/install.sh | sh

When done, the install script prints out instructions for running and starting code-server.

We also have an in-depth setup and configuration guide.

We're working on a cloud platform that makes deploying and managing code-server easier. Consider running code-server with the beta flag --link if you don't want to worry about

  • TLS
  • Authentication
  • Port Forwarding
$ code-server --link
Proxying code-server, you can access your IDE at https://valmar-jon.cdr.co

FAQ

See ./docs/FAQ.md.

Want to help?

See CONTRIBUTING for details.

Hiring

Interested in working at Coder? Check out our open positions!

For Organizations

Visit our website for more information about remote development for your organization or enterprise.