VS Code in the browser
Go to file
Asher 5ebb096db5
Get terminals working
- Instead of a single listener per terminal that handles all events VS
  Code now has a single listener per event that handles that event for
  all terminals.
- Refactor Terminal to extend TerminalProcess to avoid duplicating
  methods. This required some modifications to TerminalProcess to access
  the pid and title and to set the ID.
- Remove our async change to shutdown. This was necessary to avoid
  disposing too early but shutdown already calls dispose so it turns out
  we didn't need to call it ourselves.
- Rename methods to match the command strings.
- Fix getting system shell (uses process.env).
- Use a single bufferer. Since it already supports buffering for
  multiple terminals there's no need to have one per terminal.
- Remove replay/reconnect logic. It's broken and unused so there doesn't
  seem much point in trying to refactor it to fit the changes right now.

While terminals work now there are still a lot of todos.
2021-04-13 16:35:13 -05:00
.github dev(ranger): fix typo 2021-04-08 15:12:24 -07:00
.tours refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
ci fix: use curl to install nfpm 2021-04-08 14:05:30 -07:00
docs chore(release): bump version to 3.9.3 2021-04-08 11:18:56 -07:00
lib/vscode Get terminals working 2021-04-13 16:35:13 -05:00
src Fix tsc watch restarting when it shouldn't 2021-04-01 10:58:56 -05:00
test refactor: check for editor consistently in tests 2021-04-06 15:46:58 -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 chore: update gitignore with test dirs 2021-03-12 12:00:57 -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
LICENSE.txt Shake CI and docs up 2020-02-14 19:46:17 -05: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
install.sh chore(release): bump version to 3.9.3 2021-04-08 11:18:56 -07:00
package.json 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 Squashed 'lib/vscode/' changes from fd6f3bce670..ead2c2ab0f5 2021-04-09 11:32:26 +05:30

README.md

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.