f4fc2ebecf
* chore(release): bump version to 4.5.1 * chore: bump helm chart * chore: update CHANGELOG * Revert "chore: bump helm chart" This reverts commit703b03b665. * chore: bump helm chart to 3.0.0 * revert: remove bad change to manifes.json icon * fix(ci): add package.json.version to code cachekey Before this, creating a release sometimes prevented vscode from rebuilding and using the cache instead. Now we use the package.json.version in the cache key to "bust" the cache if the package.json version is updated (aka a release). Fixes #5316 * Update .github/workflows/ci.yaml Co-authored-by: Asher <ash@coder.com> * fixup: formatting * Revert "refactor: remove version check e2e test" This reverts commitb23c398b7d. Co-authored-by: Asher <ash@coder.com>
66 lines
2.5 KiB
Markdown
66 lines
2.5 KiB
Markdown
# Collaboration
|
|
|
|
With third-party extensions, you can use code-server to collaborate with other developers in real time.
|
|
|
|
## Code sharing using Duckly
|
|
|
|
[Duckly](https://duckly.com/) allows you to share your code in real-time even with people using different IDEs (like JetBrains and VSCode).
|
|
|
|
- Cross-IDE support,
|
|
- Real-time typing,
|
|
- P2P encrypted,
|
|
- Voice and audio chat,
|
|
- Terminal sharing
|
|
|
|
### Installing the Duckly Extension
|
|
|
|
Duckly uses an extension to provide real time sharing features
|
|
|
|
1. Install the Duckly extension from OpenVSX on `code-server`.
|
|
|
|
```bash
|
|
SERVICE_URL=https://open-vsx.org/vscode/gallery \
|
|
ITEM_URL=https://open-vsx.org/vscode/item \
|
|
code-server --install-extension gitduck.code-streaming
|
|
```
|
|
|
|
2. Refresh you `code-server` window. You should now be able to see the Duckly extension.
|
|
|
|
### Sharing with Duckly
|
|
|
|
As `code-server` is based on VS Code, you can follow the steps described on Duckly's [Pair programming with VS Code](https://duckly.com/tools/vscode) page and skip the installation step.
|
|
|
|
## Code sharing using CodeTogether
|
|
|
|
[CodeTogether](https://www.codetogether.com/) is a real-time cross-IDE replacement for Microsoft Live Share providing:
|
|
|
|
- Cross-IDE support - between VS Code, Eclipse, IntelliJ and IDEs based on them (browser or desktop)
|
|
- Real-time editing - shared or individual cursors for pairing, mobbing, swarming, or whatever
|
|
- P2P encrypted - servers can't decrypt the traffic ([Security Details](https://codetogether.com/download/security/))
|
|
- SaaS or [On-premises](https://codetogether.com/on-premises/) options
|
|
- Shared servers, terminals, and consoles
|
|
- Unit Testing - with support for Red, Green, Refactor TDD
|
|
- Joining via a web browser or your preferred IDE
|
|
- Free unlimited 1 hour sessions with 4 participants
|
|
- Multiple plans including [free or paid options](https://www.codetogether.com/pricing/)
|
|
|
|
### Installing the CodeTogether extension
|
|
|
|
1. Install the CodeTogether extension from OpenVSX on `code-server`.
|
|
|
|
```sh
|
|
SERVICE_URL=https://open-vsx.org/vscode/gallery \
|
|
ITEM_URL=https://open-vsx.org/vscode/item \
|
|
code-server --install-extension genuitecllc.codetogether
|
|
```
|
|
|
|
2. CodeTogether requires VS Code's proposed API to run. Start code-server with the following flag:
|
|
|
|
```sh
|
|
code-server --enable-proposed-api genuitecllc.codetogether
|
|
```
|
|
|
|
Another option would be to add a value in code-server's [config file](https://coder.com/docs/code-server/v4.5.1/FAQ#how-does-the-config-file-work).
|
|
|
|
3. Refresh code-server and navigate to the CodeTogether icon in the sidebar to host or join a coding session.
|