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 6275520348
Fix incorrect argon2 target in arm builds (#6453)
* Fix building from source on arm

Not building from source causes argon2 to pull the wrong arch, so we
have to build from source.

But building from source is causing the new Kerberos module to fail on
arm64 and keytar to fail on both.

The latter has been very difficult to debug because the GitHub image
provides a different result to containers based on Ubuntu 20.04.
Because of this, use a container instead.

Use debian:buster as the container because it is easier to set up the
architecture sources (no need to modify the sources) and because it
seems to come with glibc 2.28 rather than 2.31.

Also use the exact version of Node (18.15.0) for reproducibility.

* Set owner and group during tar to zero

Otherwise you get IDs that can cause (benign) errors while extracting,
which might be confusing.  At the very least, I did not see these errors
from previous tars (although they seem to use 1001).

There is no guarantee what IDs might exist so 0 seems the most
reasonable.
2023-09-27 19:17:47 -08:00
.github Fix incorrect argon2 target in arm builds (#6453) 2023-09-27 19:17:47 -08:00
.tours docs: rename master to main in all github doc links (#5190) 2022-05-11 14:39:57 -07:00
ci Fix incorrect argon2 target in arm builds (#6453) 2023-09-27 19:17:47 -08:00
docs Add .local mount to example Docker command (#6419) 2023-09-22 17:07:07 -08:00
lib Update to VS Code 1.82.2 (#6436) 2023-09-20 15:33:28 -08:00
patches Refresh proxy URI patch 2023-09-26 12:19:13 -08:00
src Enable secret storage (#6450) 2023-09-26 08:35:41 -08:00
test Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -08: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 Fix cross-compilation (#6441) 2023-09-21 23:21:01 -08: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.17.0 2023-09-22 17:49:40 -08: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 Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -08: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.