- Notifications
You must be signed in to change notification settings - Fork927
feat: one-line install script#1924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
006a805
2724aef
f7a5ee8
c3505ed
5d23600
936c466
086e30e
3a65b94
26ab867
3568085
a022e3b
038dc8c
fa59da0
bec5584
c308d60
8989211
cf1912a
a611c7b
a16a04a
6879752
8cba04c
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -52,6 +52,8 @@ jobs: | ||
- uses: actions/checkout@v3 | ||
- name: Run ShellCheck | ||
uses: ludeeus/action-shellcheck@1.1.0 | ||
env: | ||
SHELLCHECK_OPTS: --external-sources | ||
Comment on lines +55 to +56 MemberAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. This resolved some warnings around unspecified inputs. Seehttps://www.mankier.com/1/shellcheck#-x andkoalaman/shellcheck#902 The error was only for `/etc/os-release` in the script$makelint/shellcheckIninstall.shline424:./etc/os-release^-------------^SC1091:Notfollowing:/etc/os-releasewasnotspecifiedasinput(seeshellcheck-x).Ininstall.shline450:./etc/os-release^-------------^SC1091:Notfollowing:/etc/os-releasewasnotspecifiedasinput(seeshellcheck-x). | ||
with: | ||
ignore: node_modules | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -2,6 +2,58 @@ | ||
This article walks you through the various ways of installing and deploying Coder. | ||
## install.sh | ||
The easiest way to install Coder is to use our [install script](https://github.com/coder/coder/main/install.sh) for Linux and macOS. The install script | ||
attempts to use the system package manager detection-reference if possible. | ||
You can preview what occurs during the install process: | ||
```bash | ||
curl -L https://coder.com/install.sh | sh -s -- --dry-run | ||
``` | ||
To install, run: | ||
```bash | ||
curl -L https://coder.com/install.sh | sh | ||
``` | ||
> If you're concerned about the install script's use of `curl | sh` and the | ||
> security implications, please see [this blog | ||
> post](https://sandstorm.io/news/2015-09-24-is-curl-bash-insecure-pgp-verified-install) | ||
> by [sandstorm.io](https://sandstorm.io). | ||
You can modify the installation process by including flags. Run the help command for reference: | ||
```bash | ||
curl -L https://coder.com/install.sh | sh -s -- --help | ||
``` | ||
## System packages | ||
Coder publishes the following system packages [in GitHub releases](https://github.com/coder/coder/releases): | ||
- .deb (Debian, Ubuntu) | ||
- .rpm (Fedora, CentOS, RHEL, SUSE) | ||
- .apk (Alpine) | ||
Once installed, you can run Coder as a system service: | ||
```sh | ||
# Specify a PostgreSQL database | ||
# in the configuration first: | ||
sudo vim /etc/coder.d/coder.env | ||
sudo service coder restart | ||
``` | ||
Or run a **temporary deployment** with dev mode (all data is in-memory and destroyed on exit): | ||
```sh | ||
coder server --dev | ||
``` | ||
## docker-compose | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. @khorne3 I feel like this section is a bit too long. Thoughts on stopping after Contributor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. I think after | ||
Before proceeding, please ensure that you have both Docker and the [latest version of | ||
@@ -40,62 +92,34 @@ Coder](https://github.com/coder/coder/releases) installed. | ||
ghcr.io/coder/coder:v0.5.10 | ||
``` | ||
1. Follow the on-screen instructions to create your first template and workspace | ||
## Manual | ||
We publish self-contained .zip and .tar.gz archives in [GitHub releases](https://github.com/coder/coder/releases). The archives bundle `coder` binary. | ||
1. Download the [release archive](https://github.com/coder/coder/releases) appropriate for your operating system | ||
1.Unzipthefolder you just downloaded,andmove the `coder` executable to a location that's on your `PATH` | ||
```sh | ||
# ex. MacOS and Linux | ||
mvcoder/usr/local/bin | ||
``` | ||
> Windows users: see [this guide](https://answers.microsoft.com/en-us/windows/forum/all/adding-path-variable/97300613-20cb-4d85-8d0e-cc9d3549ba23) for adding folders to `PATH`. | ||
1. Start a Coder server | ||
To run a **temporary deployment**, start with dev mode (all data is in-memory and destroyed on exit): | ||
```bash | ||
coderserver --dev | ||
``` | ||
To run a **production deployment** with PostgreSQL: | ||
```bash | ||
CODER_PG_CONNECTION_URL="postgres://<username>@<host>/<database>?password=<password>" \ | ||
coder server | ||
``` | ||
Uh oh!
There was an error while loading.Please reload this page.