5ebb096db5
- 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. |
||
|---|---|---|
| .github | ||
| .tours | ||
| ci | ||
| docs | ||
| lib/vscode | ||
| src | ||
| test | ||
| typings | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintrc.yaml | ||
| .gitattributes | ||
| .gitignore | ||
| .prettierrc.yaml | ||
| .stylelintrc.yaml | ||
| LICENSE.txt | ||
| README.md | ||
| ThirdPartyNotices.txt | ||
| install.sh | ||
| package.json | ||
| tsconfig.json | ||
| yarn.lock | ||
README.md
code-server · 
Run VS Code on any machine anywhere and access it in the browser.
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:
- Using the install script, which automates most of the process. The script uses the system package manager (if possible)
- Manually installing code-server; see Installation for instructions applicable to most use cases
- 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.
code-server --link
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.