Go to file
Asher acc50a5d36
Update dependencies and force-update qs (#6440)
* Update dependencies and force-update qs

This is mainly an attempt to get rid of as many resolutions as possible
since it seems they are unnecessary except for qs (according to yarn/npm
audit).

For qs use 6.9.7 since Express is using 6.9.6 and that matches the most
closely.

Also add overrides since this is npm's version of yarn's resolutions and
we need it for the shrinkwrap to generate with the right dependencies.

Decided to keep pinning @types/node as well although I am not sure it is
necessary.  Express is pulling in v20 types.  Since this is
development-only we only need it in resolutions.

* Run formatter

Some rules seem to have changed with the dependency updates.

* Replace deprecated bodyParser.json() usage

* Audit npm shrinkwrap as well

* Skip installing dependencies in audit

It seems the tools only require the lock files.

* Fix tests when using ipv6

* Add missing openssl dependency to flake
2023-09-21 16:13:34 -08:00
.github Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -08:00
.tours docs: rename master to main in all github doc links (#5190) 2022-05-11 14:39:57 -07:00
ci Update to VS Code 1.82.2 (#6436) 2023-09-20 15:33:28 -08:00
docs Bump minimum glibc to 2.28 (#6439) 2023-09-21 13:42:17 -08:00
lib Update to VS Code 1.82.2 (#6436) 2023-09-20 15:33:28 -08:00
patches Update to VS Code 1.82.2 (#6436) 2023-09-20 15:33:28 -08:00
src Update dependencies and force-update qs (#6440) 2023-09-21 16:13:34 -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 chore: upgrade developmemt node version to v16 (#5167) 2022-05-06 09:57:19 -05: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.16.1 2023-07-31 11:21:45 -08:00
LICENSE chore: remove file ext. from LICENSE (#5070) 2022-04-07 10:36:33 -07:00
ThirdPartyNotices.txt Add ThirdPartyNotices.txt 2020-07-16 19:01:09 -06: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
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
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

docs/README.md

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.