|
11 | 11 | - [Version updates to Code](#version-updates-to-code)
|
12 | 12 | - [Patching Code](#patching-code)
|
13 | 13 | - [Build](#build)
|
| 14 | + - [Creating a Standalone Release](#creating-a-standalone-release) |
14 | 15 | - [Troubleshooting](#troubleshooting)
|
15 | 16 | - [I see "Forbidden access" when I load code-server in the browser](#i-see-forbidden-access-when-i-load-code-server-in-the-browser)
|
16 |
| - - ["Can only have one anonymous define call per script"](#can-only-have-one-anonymous-define-call-per-script) |
| 17 | + - ["Can only have one anonymous define call per script"](#can-only-have-one-anonymous-define-call-per-script) |
17 | 18 | - [Help](#help)
|
18 | 19 | - [Test](#test)
|
19 | 20 | - [Unit tests](#unit-tests)
|
@@ -170,6 +171,22 @@ yarn package
|
170 | 171 | > If you need your builds to support older distros, run the build commands
|
171 | 172 | > inside a Docker container with all the build requirements installed.
|
172 | 173 |
|
| 174 | +#### Creating a Standalone Release |
| 175 | + |
| 176 | +Part of the build process involves creating standalone releases. At the time of |
| 177 | +writing, we do this for the following platforms/architectures: |
| 178 | + |
| 179 | +- Linux amd64 (.tar.gz, .deb, and .rpm) |
| 180 | +- Linux arm64 (.tar.gz, .deb, and .rpm) |
| 181 | +- Linux arm7l (.tar.gz) |
| 182 | +- Linux armhf.deb |
| 183 | +- Linux armhf.rpm |
| 184 | +- macOS amd64 (Intel-based) |
| 185 | + |
| 186 | +Currently, these are compiled in CI using the `yarn release-standalone` command |
| 187 | +in the `release.yaml` workflow. We then upload them to the draft release and |
| 188 | +distribute via GitHub Releases. |
| 189 | + |
173 | 190 | ### Troubleshooting
|
174 | 191 |
|
175 | 192 | #### I see "Forbidden access" when I load code-server in the browser
|
|
0 commit comments