a
/
code-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Rename self contained release to static release

This commit is contained in:
Anmol Sethi 2020-05-17 16:59:09 -04:00
parent 6a25b3bfa0
commit e0dbd8f74a
No known key found for this signature in database
GPG Key ID: 8CEF1878FF10ADEB
3 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -70,7 +70,7 @@ docker run -it -p 127.0.0.1:8080:8080 \
codercom/code-server:latest codercom/code-server:latest
``` ```
### Self contained releases ### Static releases
We publish self contained `.tar.gz` archives for every release on [github](https://github.com/cdr/code-server/releases). We publish self contained `.tar.gz` archives for every release on [github](https://github.com/cdr/code-server/releases).
They bundle the node binary and compiled native modules. They bundle the node binary and compiled native modules.
@ -81,7 +81,7 @@ They bundle the node binary and compiled native modules.
Add the code-server `bin` directory to your `$PATH` to easily execute `code-server` without the full path every time. Add the code-server `bin` directory to your `$PATH` to easily execute `code-server` without the full path every time.
Here is an example script for installing and using a self-contained `code-server` release on Linux: Here is an example script for installing and using a static `code-server` release on Linux:
```bash ```bash
curl -sSL https://github.com/cdr/code-server/releases/download/3.3.0/code-server-3.3.0-linux-amd64.tar.gz | sudo tar -C /usr/local -xz curl -sSL https://github.com/cdr/code-server/releases/download/3.3.0/code-server-3.3.0-linux-amd64.tar.gz | sudo tar -C /usr/local -xz

5
ci/README.md
View File

@ -20,7 +20,8 @@ Make sure you have `$GITHUB_TOKEN` set and [hub](https://github.com/github/hub)
the updated version. the updated version.
1. Summarize the major changes in the release notes and link to the relevant issues. 1. Summarize the major changes in the release notes and link to the relevant issues.
4. Wait for the artifacts in step 2 to build. 4. Wait for the artifacts in step 2 to build.
5. Run `yarn release:github-assets` to download the `release-packages` artifact and then upload them to the draft release. 5. Run `yarn release:github-assets` to download the `release-packages` artifact and then
upload them to the draft release.
6. Run some basic sanity tests on one of the released packages. 6. Run some basic sanity tests on one of the released packages.
7. Publish the release. 7. Publish the release.
1. CI will automatically grab the artifacts and then: 1. CI will automatically grab the artifacts and then:
@ -123,7 +124,7 @@ Helps avoid clobbering the CI configuration.
- Runs the release process. - Runs the release process.
- Generates the npm package at `./release`. - Generates the npm package at `./release`.
- [./steps/release-static.sh](./steps/release-static.sh) - [./steps/release-static.sh](./steps/release-static.sh)
- Takes the output of the previous script and generates a self-contained release and - Takes the output of the previous script and generates a static release and
release packages into `release-packages`. release packages into `release-packages`.
- [./steps/publish-npm.sh](./steps/publish-npm.sh) - [./steps/publish-npm.sh](./steps/publish-npm.sh)
- Grabs the `npm-package` release artifact for the current commit and publishes it on npm. - Grabs the `npm-package` release artifact for the current commit and publishes it on npm.

2
doc/CONTRIBUTING.md
View File

@ -57,7 +57,7 @@ yarn release:static
yarn test:static-release yarn test:static-release
yarn package yarn package
# The static release is in ./release-static # The static release is in ./release-static
# .deb, .rpm and the self-contained archive are in ./release-packages # .deb, .rpm and the static archive are in ./release-packages
``` ```
## Structure ## Structure