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 e8443e2602
Fix helpers not working in e2e tests
It errors that jest is not defined so put it behind a function instead
of immediately creating the mock (this is probably a better pattern
anyway).

The constant tests had to be reworked a little. Since the logger mock is
hoisted it runs before createLoggerMock is imported. I moved it into a
beforeAll which means the require call also needed to be moved
there (since we need to mock the logger before requiring the constants
or it'll pull the non-mocked logger).

This means getPackageJson needs to be a let and assigned afterward. To
avoid having to define a type for getPackageJson I just added a let var
set to the type of the imported constants file and modified the other
areas to use the same paradigm.

I also replaced some hardcoded strings with the mocked package.json
object.
2021-05-06 15:01:35 -05:00
.github refactor(ci): split audit from prebuild (#3298) 2021-05-07 00:32:10 +05:30
.tours refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
ci feat(ci/build): support arm64 for cloud-agent (#3294) 2021-05-05 21:53:30 +05:30
docs docs(security): add section for tools 2021-05-05 11:24:31 -07:00
lib/vscode Share common util code with VS Code 2021-05-04 13:29:40 -05:00
src Refactor integration tests to use main entry point 2021-05-05 12:24:41 -05:00
test Fix helpers not working in e2e tests 2021-05-06 15:01:35 -05:00
typings Share common util code with VS Code 2021-05-04 13:29:40 -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 fix: remove eslint-plugin-jest-playwright 2021-04-29 10:46:14 -07:00
.gitattributes browser: Add favicon.afdesign 2021-01-08 23:03:34 -05:00
.gitignore fix: update path for e2e videos 2021-04-15 11:46:45 -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
install.sh chore(release): bump version to 3.9.3 2021-04-08 11:18:56 -07:00
LICENSE.txt Shake CI and docs up 2020-02-14 19:46:17 -05:00
package.json fix: coveragePathIgnorePatterns to /out 2021-05-06 11:53:17 -07:00
README.md docs(readme): add codecov badge 2021-04-26 14:13:02 -07:00
ThirdPartyNotices.txt Add ThirdPartyNotices.txt 2020-07-16 19:01:09 -06:00
tsconfig.json chore: update ts config and jest config 2021-01-25 16:34:32 -07:00
yarn.lock chore(deps-dev): bump @types/node from 12.20.11 to 12.20.12 (#3292) 2021-05-05 18:05:04 +05:30

code-server · "GitHub Discussions" "Join us on Slack" Twitter Follow

codecov 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.