Archived
1
0
VS Code in the browser
This repository has been archived on 2024-09-09. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Asher 73cb236535
Add back local storage patch
And fix the workspace bug.  It is caused by an issue with how some
global variables are being used asynchronously and is exacerbated by the
delay reading settings from the remote introduces.

1. The workspace is created and is marked as not initialized.
2. The configuration's change handler is triggered, and now
   initialization is complete.
3. The handler tries to set the global workspace variable to initialized
   but the workspace has not been set yet so we get an undefined error.
4. The workspace global is now set, but it is set to the old value with
   initialized still set to false.
5. Workspace is never marked as initialized until something else
   triggers the on change handler again.

Fixes #3061, and closes #6546.

My guess is this logic changed in one of the VS Code updates,
introducing this async bug but never getting caught probably because for
them the settings are always local thus minimal delay.
2023-11-27 17:25:38 -09:00
.github Fix node-gyp failure on macOS (#6537) 2023-11-16 10:10:36 -09:00
.tours docs: rename master to main in all github doc links (#5190) 2022-05-11 14:39:57 -07:00
ci Release v4.19.0 2023-11-20 07:29:25 -09:00
docs Update Termux docs on how to enable keyboard shortcuts and tab key (#6539) 2023-11-20 08:16:17 -09:00
lib Update Code to 1.84.2 (#6524) 2023-11-14 13:44:21 -09:00
patches Add back local storage patch 2023-11-27 17:25:38 -09:00
src Modify manifest for window control overlay support (#6468) 2023-10-02 18:03:37 +00:00
test Use machine settings for e2e tests 2023-11-20 15:42:34 -09:00
typings chore(deps): update dependency @types/node to v16 (#5170) 2022-08-10 16:15:52 -05:00
.dockerignore Simplify packaging and improve scripts 2020-05-08 01:04:24 -04:00
.editorconfig Revert .editorconfig (#4640) 2021-12-16 15:30:07 -06:00
.eslintrc.yaml chore: replace eslint-import-resolver-alias with eslint-import-resolver-typescript (#4546) 2021-12-07 14:39:01 -07:00
.gitattributes browser: Add favicon.afdesign 2021-01-08 23:03:34 -05:00
.gitignore chore(Code): upgrade to 1.65 (#5047) 2022-03-30 18:33:58 -05:00
.gitmodules chore: move to patches (#4997) 2022-03-22 15:07:14 -05:00
.node-version Set Node version in a single place (#6534) 2023-11-14 12:45:56 -09:00
.nvmrc chore: Update dependency requirements. Fix node version manager. 2021-07-21 14:32:16 -04:00
.prettierignore release: 4.9.0 (#5772) 2022-12-06 13:28:27 -07:00
.prettierrc.yaml chore(prettier): ignore lib/vscode (#5347) 2022-07-15 21:13:13 +00:00
CHANGELOG.md Release v4.19.0 2023-11-20 07:29:25 -09:00
flake.lock Update to 1.78.2 (#6201) 2023-05-15 15:44:03 -08:00
flake.nix Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -08:00
install.sh Update to VS Code 1.82.2 (#6436) 2023-09-20 15:33:28 -08:00
LICENSE chore: remove file ext. from LICENSE (#5070) 2022-04-07 10:36:33 -07:00
package.json Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -08:00
renovate.json chore: use matchUpdateTypes (#5942) 2023-01-04 23:08:39 +00:00
ThirdPartyNotices.txt Add ThirdPartyNotices.txt 2020-07-16 19:01:09 -06:00
tsconfig.json feat: add i18n in login page (#5947) 2023-01-13 17:42:49 +00:00
yarn.lock chore: bump @typescript-eslint/eslint-plugin from 6.7.2 to 6.11.0 (#6533) 2023-11-14 09:38:31 -09:00

code-server

"GitHub Discussions" "Join us on Slack" Twitter Follow codecov See latest

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

Screenshot 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

See requirements for minimum specs, as well as instructions on how to set up a Google VM on which you can install code-server.

TL;DR: Linux machine with WebSockets enabled, 1 GB RAM, and 2 vCPUs

Getting started

There are four ways to 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
  3. Deploy code-server to your team with coder/coder
  4. Using our one-click buttons and guides to deploy code-server to a cloud provider

If you 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.

Note

To manage code-server for a team on your infrastructure, see: coder/coder

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

Questions?

See answers to frequently asked questions.

Want to help?

See Contributing for details.

Hiring

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

For Organizations

Want remote development for your organization or enterprise? Visit our website to learn more about Coder.