9e80322fe5
The path.nsh script in the NSIS installer provided methods for adding paths to the PATH and removing them. It would do this by reading the current PATH value from the registry, adding the new value (if it doesn't exist) and then writing it to the registry. Unfortunately, it would read from the user's PATH and write the updated result to the system PATH, which would remove important PATH entries like the following in the process: - C:\Windows\System32 - C:\Windows - C:\Windows\System32\wbem - C:\Windows\System32\WindowsPowerShell\v1.0 - C:\Windows\System32\OpenSSH - C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR - C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common and would copy all user environment variables in their place. The variables listed above were the ones missing from my machine when I compared with a friend's machine. Recommended course of action for affected users: 1. Add the paths listed above to your system PATH if they aren't there already and exist on your system. 2. Remove any paths that are in your user's PATH from your system PATH. The existing installers for the last couple of versions of Coder have been yanked from GitHub releases and this message will be included in the release notes for the next patch. Thanks to @cmor for finding and reporting this bug in #5240. |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| agent | ||
| buildinfo | ||
| cli | ||
| cmd | ||
| coderd | ||
| codersdk | ||
| cryptorand | ||
| docs | ||
| dogfood | ||
| enterprise | ||
| examples | ||
| helm | ||
| loadtest | ||
| provisioner | ||
| provisionerd | ||
| provisionersdk | ||
| pty | ||
| scripts | ||
| site | ||
| tailnet | ||
| testutil | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yaml | ||
| ADOPTERS.md | ||
| Dockerfile | ||
| LICENSE | ||
| LICENSE.enterprise | ||
| Makefile | ||
| README.md | ||
| coder.env | ||
| coder.service | ||
| docker-compose.yaml | ||
| flake.lock | ||
| flake.nix | ||
| go.mod | ||
| go.sum | ||
| install.sh | ||
| preinstall.sh | ||
| shell.nix | ||
README.md
Coder
Software development on your infrastructure. Offload your team's development from local workstations to cloud servers. Onboard developers in minutes. Build, test and compile at the speed of the cloud. Keep your source code and data behind your firewall.
"By leveraging Terraform, Coder lets developers run any IDE on any compute platform including on-prem, AWS, Azure, GCP, DigitalOcean, Kubernetes, Docker, and more, with workspaces running on Linux, Windows, or Mac." - Kevin Fishner Chief of Staff at HashiCorp
Manage less
- Ensure your entire team is using the same tools and resources
- Rollout critical updates to your developers with one command
- Automatically shut down expensive cloud resources
- Keep your source code and data behind your firewall
Code more
- Build and test faster
- Leveraging cloud CPUs, RAM, network speeds, etc.
- Access your environment from any place on any client (even an iPad)
- Onboard instantly then stay up to date continuously
Recommended Reading
- How our development team shares one giant bare metal machine
- Laptop development is dead: why remote development is the future
- Learn how Palantir improved build times by 78% with coder.
- A software development environment is not just a container.
- What Coder is not.
Getting Started
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.
To install, run:
curl -L https://coder.com/install.sh | sh
You can preview what occurs during the install process:
curl -L https://coder.com/install.sh | sh -s -- --dry-run
You can modify the installation process by including flags. Run the help command for reference:
curl -L https://coder.com/install.sh | sh -s -- --help
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 The embedded database is great for trying out Coder with small deployments, but do consider using an external database for increased assurance and control.
Use coder --help to get a complete list of flags and environment variables. Use our quickstart guide for a full walkthrough.
Documentation
Visit our docs here.
Comparison
Please file an issue if any information is out of date. Also refer to: What Coder is not.
| Tool | Type | Delivery Model | Cost | Environments |
|---|---|---|---|---|
| Coder | Platform | OSS + Self-Managed | Pay your cloud | All Terraform resources, all clouds, multi-architecture: Linux, Mac, Windows, containers, VMs, amd64, arm64 |
| code-server | Web IDE | OSS + Self-Managed | Pay your cloud | Linux, Mac, Windows, containers, VMs, amd64, arm64 |
| Coder (Classic) | Platform | Self-Managed | Pay your cloud + license fees | Kubernetes Linux Containers |
| GitHub Codespaces | Platform | SaaS | 2x Azure Compute | Linux Virtual Machines |
Last updated: 5/27/22
Community and Support
Join our community on Discord and Twitter!
Suggest improvements and report problems
Contributing
If you're using Coder in your organization, please try to add your company name to the ADOPTERS.md. It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
Read the contributing docs.
Find our list of contributors here.