@@ -4,27 +4,20 @@ and macOS.
4
4
5
5
To install, run:
6
6
7
- ``` shell
8
- # This will automatically use supported package managers when available
7
+ ``` bash
9
8
curl -fsSL https://coder.com/install.sh | sh
10
9
```
11
10
12
- To install without using a system package manager:
13
-
14
- ``` shell
15
- curl -fsSL https://coder.com/install.sh | sh -s -- --method standalone
16
- ```
17
-
18
11
You can preview what occurs during the install process:
19
12
20
- ``` shell
13
+ ``` bash
21
14
curl -fsSL https://coder.com/install.sh | sh -s -- --dry-run
22
15
```
23
16
24
17
You can modify the installation process by including flags. Run the help command
25
18
for reference:
26
19
27
- ``` shell
20
+ ``` bash
28
21
curl -fsSL https://coder.com/install.sh | sh -s -- --help
29
22
```
30
23
@@ -34,87 +27,6 @@ manually via `coder server` or as a system package.
34
27
By default, the Coder server runs on ` http://127.0.0.1:3000 ` and uses a
35
28
[ public tunnel] ( ../admin/configure.md#tunnel ) for workspace connections.
36
29
37
- ## ` PATH ` conflicts
38
-
39
- It's possible to end up in situations where you have multiple ` coder ` binaries
40
- in your ` PATH ` , and your system may use a version that you don't intend. Your
41
- ` PATH ` is a variable that tells your shell where to look for programs to run.
42
-
43
- You can check where all of the versions are by running ` which -a coder ` .
44
-
45
- For example, a common conflict on macOS might be between a version installed by
46
- Homebrew, and a version installed manually to the /usr/local/bin directory.
47
-
48
- ``` console
49
- $ which -a coder
50
- /usr/local/bin/coder
51
- /opt/homebrew/bin/coder
52
- ```
53
-
54
- Whichever binary comes first in this list will be used when running ` coder `
55
- commands.
56
-
57
- ### Reordering your ` PATH `
58
-
59
- If you use bash or zsh, you can update your ` PATH ` like this:
60
-
61
- ``` shell
62
- # You might want to add this line to the end of your ~/.bashrc or ~/.zshrc file!
63
- export PATH=" /opt/homebrew/bin:$PATH "
64
- ```
65
-
66
- If you use fish, you can update your ` PATH ` like this:
67
-
68
- ``` shell
69
- # You might want to add this line to the end of your ~/.config/fish/config.fish file!
70
- fish_add_path " /opt/homebrew/bin"
71
- ```
72
-
73
- > ℹ If you ran install.sh with a ` --prefix ` flag, you can replace
74
- > ` /opt/homebrew ` with whatever value you used there. Make sure to leave the
75
- > ` /bin ` at the end!
76
-
77
- Now we can observe that the order has changed:
78
-
79
- ``` console
80
- $ which -a coder
81
- /opt/homebrew/bin/coder
82
- /usr/local/bin/coder
83
- ```
84
-
85
- ### Removing unneeded binaries
86
-
87
- If you want to uninstall a version of ` coder ` that you installed with a package
88
- manager, you can run whichever one of these commands applies:
89
-
90
- ``` shell
91
- # On macOS, with Homebrew installed
92
- brew uninstall coder
93
- ```
94
-
95
- ``` shell
96
- # On Debian/Ubuntu based systems
97
- sudo dpkg -r coder
98
- ```
99
-
100
- ``` shell
101
- # On Fedora/RHEL-like systems
102
- sudo rpm -e coder
103
- ```
104
-
105
- ``` shell
106
- # On Alpine
107
- sudo apk del coder
108
- ```
109
-
110
- If the conflicting binary is not installed by your system package manager, you
111
- can just delete it.
112
-
113
- ``` shell
114
- # You might not need `sudo`, depending on the location
115
- sudo rm /usr/local/bin/coder
116
- ```
117
-
118
30
## Next steps
119
31
120
32
- [ Configuring Coder] ( ../admin/configure.md )
0 commit comments