b79785c86f
Moves monitoring of the agent v2 API connection to the yamux layer. Present behavior monitors this at the websocket layer, and closes the websocket on completion. This can cause yamux to hit unexpected errors since the connection is closed underneath it. This might be the cause of yamux errors that some customers are seeing  In any case, it's more graceful to close yamux first and let yamux close the underlying websocket. That should limit yamux error logging to truly unexpected/error cases. The only downside is that the yamux `Close()` doesn't accept a reason, so if the agent becomes outdated and we close the API connection, the agent just sees the connection close without a reason. I'm not sure we log this at the agent anyway, but it would be nice. I think more accurate logging on Coderd are more important. I've also added some logging when the monitor disconnects for reasons other than the context being canceled (e.g. agent outdated, failed pings). |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| agent | ||
| buildinfo | ||
| cli | ||
| cmd | ||
| coderd | ||
| codersdk | ||
| cryptorand | ||
| docs | ||
| dogfood | ||
| enterprise | ||
| examples | ||
| helm | ||
| offlinedocs | ||
| provisioner | ||
| provisionerd | ||
| provisionersdk | ||
| pty | ||
| scaletest | ||
| scripts | ||
| site | ||
| tailnet | ||
| testutil | ||
| .dockerignore | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yaml | ||
| .prettierignore | ||
| .prettierignore.include | ||
| .prettierrc.yaml | ||
| .swaggo | ||
| LICENSE | ||
| LICENSE.enterprise | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| coder.env | ||
| docker-compose.yaml | ||
| flake.lock | ||
| flake.nix | ||
| go.mod | ||
| go.sum | ||
| install.sh | ||
| package.json | ||
| pnpm-lock.yaml | ||
| release.key | ||
| shell.nix | ||
README.md
Coder enables organizations to set up development environments in their public or private cloud infrastructure. Cloud development environments are defined with Terraform, connected through a secure high-speed Wireguard® tunnel, and are automatically shut down when not in use to save on costs. Coder gives engineering teams the flexibility to use the cloud for workloads that are most beneficial to them.
- Define cloud development environments in Terraform
- EC2 VMs, Kubernetes Pods, Docker Containers, etc.
- Automatically shutdown idle resources to save on costs
- Onboard developers in seconds instead of days
Quickstart
The most convenient way to try Coder is to install it on your local machine and experiment with provisioning cloud development environments using Docker (works on Linux, macOS, and Windows).
# First, install Coder
curl -L https://coder.com/install.sh | sh
# Start the Coder server (caches data in ~/.cache/coder)
coder server
# Navigate to http://localhost:3000 to create your initial user
# Create a Docker template, and provision a workspace
Install
The easiest way to install Coder is to use our
install script for Linux
and macOS. For Windows, use the latest ..._installer.exe file from GitHub
Releases.
curl -L https://coder.com/install.sh | sh
You can run the install script with --dry-run to see the commands that will be used to install without executing them. You can modify the installation process by including flags. Run the install script with --help for reference.
See install for additional methods.
Once installed, you can start a production deployment1 with a single command:
# Automatically sets up an external access URL on *.try.coder.app
coder server
# Requires a PostgreSQL instance (version 13 or higher) and external access URL
coder server --postgres-url <url> --access-url <url>
1 For production deployments, set up an external PostgreSQL instance for reliability.
Use coder --help to get a list of flags and environment variables. Use our install guides for a full walkthrough.
Documentation
Browse our docs here or visit a specific section below:
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- IDEs: Connect your existing editor to a workspace
- Administration: Learn how to operate Coder
- Enterprise: Learn about our paid features built for large teams
Community and Support
Feel free to open an issue if you have questions, run into bugs, or have a feature request.
Join our Discord or Slack to provide feedback on in-progress features, and chat with the community using Coder!
Contributing
Contributions are welcome! Read the contributing docs to get started.
Find our list of contributors here.
Related
We are always working on new integrations. Feel free to open an issue to request an integration. Contributions are welcome in any official or community repositories.
Official
- VS Code Extension: Open any Coder workspace in VS Code with a single click
- JetBrains Gateway Extension: Open any Coder workspace in JetBrains Gateway with a single click
- Self-Hosted VS Code Extension Marketplace: A private extension marketplace that works in restricted or airgapped networks integrating with code-server.
Community
- Provision Coder with Terraform: Provision Coder on Google GKE, Azure AKS, AWS EKS, DigitalOcean DOKS, IBMCloud K8s, OVHCloud K8s, and Scaleway K8s Kapsule with Terraform
- Coder GitHub Action: A GitHub Action that updates Coder templates
- Various Templates: Hetzner Cloud, Docker in Docker, and other templates the community has built.