3 > WebInstall is how developers install their tools
6 curl https://webinstall.dev/webi | bash
9 This repository contains the primary and community-submitted packages for
10 [webinstall.dev](https://webinstall.dev).
12 # Installer Guidelines
14 - Should install to `$HOME/.local/opt/<package>-<version>` or `$HOME/.local/bin`
15 - Should not need `sudo` (except perhaps for a one-time `setcap`, etc)
18 - Node.js: <https://github.com/webinstall/packages/tree/master/node>
19 - Golang: <https://github.com/webinstall/packages/tree/master/golang>
20 - PostgreSQL: <https://github.com/webinstall/packages/tree/master/postgres>
21 - Single-Binary Installers:
22 - Caddy: <https://github.com/webinstall/packages/tree/master/caddy>
23 - Ripgrep: <https://github.com/webinstall/packages/tree/master/ripgrep>
24 - Gitea: <https://github.com/webinstall/packages/tree/master/gitea>
25 - Convenience Scripts:
26 - Prettier: <https://github.com/webinstall/packages/tree/master/prettier>
27 - Rust-lang: <https://github.com/webinstall/packages/tree/master/rustlang>
29 <https://github.com/webinstall/packages/tree/master/vim-sensible>
33 - Contacts official release APIs for download URLs
34 - Selects the appropriate package version and archive format
35 - Installs to `$HOME/.local/`
36 - Updates `PATH` via `$HOME/.config/envman/PATH.env`
37 - Symlinks or copies current selected version
41 1. `<package>/releases.js` transforms the package's release API into a common
43 - (i.e. HTML, CSV, TAB, or JSON into a specific JSON format)
44 - common release APIs are in `_common/` (i.e. `_common/github.js`)
45 2. `_webi/bootstrap.sh` is a template that exchanges system information for a
47 - contructs a user agent with os, cpu, and utility info (i.e. `macos`,
48 `amd64`, can unpack `tar,zip,xz`)
49 3. `_webi/template.sh` is the base installer template with common functions for
51 - downloading & unpacking
53 - (re-)linking directories
54 4. `<package>/install.sh` may provide functions to override `_webi/template.sh`
56 - `curl https://webinstall.dev/<pkg>` => `bootstrap-<pkg>.sh`
57 - `bash bootstrap-<pkg>.sh` =>
58 `https://webinstall.dev/api/installers/<pkg>@<ver>.sh?formats=zip,tar`
59 - `bash install-<pkg>.sh` => download, unpack, move, link, update PATH
61 ## Creating an Installer
63 An install consists of 5 parts in 4 files:
67 - README.md (package info in frontmatter)
75 3. Version Check (semi-optional)
78 See these **examples**:
80 - https://github.com/webinstall/packages/blob/master/rg/
81 - https://github.com/webinstall/packages/blob/master/golang/
83 The `webinstall.dev` server uses the list of releases returned by
84 `<your-package>/releases.js` to generate a bash script with most necessary
85 variables and functions pre-defined.
87 You just fill in the blanks.
91 Just create an empty directory and run the tests until you get a good result.
94 git clone git@github.com:webinstall/packages.git
100 mkdir -p ./new-package/
101 node _webi/test.js ./new-package/
104 ### 1. Create Description
106 Just copy the format from any of the existing packages. It's like this:
113 homepage: https://nodejs.org
114 tagline: JavaScript V8 runtime
116 Node.jsĀ® is a JavaScript runtime built on Chrome's V8 JavaScript engine
120 node -e 'console.log("Hello, World!")'
125 ### 1. Fetch Releases
127 All you're doing in this step is just translating from one form of JSON or CSV
128 or TAB or whatever, to a format understood by `webi`.
130 - Using Github releases? See `ripgrep/releases.js` (which uses
132 - Have a special format? See `golang/releases.js` or `node/releases.js`.
139 module.exports = function (request) {
140 return github(request, owner, repo).then(function (all) {
141 // if you need to do something special, you can do it here
148 ### 2. Bash Installer
150 1. Variables _you_ can set
151 2. Functions _you_ must define
152 3. Convenience / Helper Functions
154 (optional, if needed) Bash variables that you _may_ define:
157 # Define this if the package name is different from the command name (i.e. golang => go)
158 pkg_cmd_name="foobar"
160 # These are used for symlinks, PATH, and test commands
161 pkg_dst="$HOME/.local/opt/foobar"
162 pkg_dst_cmd="$HOME/.local/opt/foobar/bin/foobar"
163 #pkg_dst_bin="$(dirname "$pkg_dst_cmd")"
165 # These are the _real_ locations for the above
166 pkg_src="$HOME/.local/opt/foobar-v$WEBI_VERSION"
167 pkg_src_cmd="$HOME/.local/opt/foobar-v$WEBI_VERSION/bin/foobar"
168 #pkg_src_bin="$(dirname "$pkg_src_cmd")"
171 (required) A version check function that strips all non-version junk
174 pkg_get_current_version() {
175 # foobar-v1.1.7 => 1.1.7
176 echo "$(foobar --version | head -n 1 | sed 's:foobar-v::')"
180 For the rest of the functions you can like copy/paste from the examples:
183 pkg_format_cmd_version() {} # Override, pretty prints version
185 pkg_link # Override, replaces webi_link()
187 pkg_pre_install() { # Override, runs any webi_* commands
188 webi_check # for $HOME/.local/opt tools
189 webi_download # for things that have a releases.js
190 webi_extract # for .xz, .tar.*, and .zip files
193 pkg_install() {} # Override, usually just needs to rename extracted folder to
194 # "$HOME/.local/opt/$pkg_cmd_name-v$WEBI_VERSION"
196 pkg_post_install() { # Override
197 webi_path_add "$pkg_dst_bin" # should probably update PATH
200 pkg_done_message() {} # Override, pretty print a success message
205 See `webi/template.sh`
207 These variables will be set by the server:
212 WEBI_HOST=https://webinstall.dev
213 WEBI_RELEASES=https://webinstall.dev/api/releases/example@v1?os=macos&arch=amd64&pretty=true
222 WEBI_PKG_URL=https://cdn.example.com/example-macos-amd64.tar.gz
223 WEBI_PKG_FILE=example-macos-amd64.tar.gz
228 PKG_OSES=macos,linux,windows
229 PKG_ARCHES=amd64,arm64,x86
234 WEBI_TMP=${WEBI_TMP:-"$(mktemp -d -t webinstall-foobar.XXXXXXXX)"}
239 webi_check # Checks to see if the selected version is already installed (and re-links if so)
240 webi_download # Downloads the selected release to $HOME/Downloads/<package-name>.tar.gz
241 webi_extract # Extracts the download to /tmp/<package-name>-<random>/
242 webi_path_add /new/path # Adds /new/path to PATH for bash, zsh, and fish
243 webi_pre_install # Runs webi_check, webi_download, and webi_extract
244 webi_install # Moves extracted files from $WEBI_TMP to $pkg_src
245 webi_link # replaces any existing symlink with the currently selected version
246 webi_post_install # Runs `webi_add_path $pkg_dst_bin`
251 - Wrap release APIs to unify and expose
252 - [ ] Support arbitrary git urls (i.e. `@github.com/node/node`)
253 - (maybe `ghi node/node` for github specifically)
254 - [ ] Support git as an archive format
259 set WEBI_HOST=https://webinstall.dev
262 Windows 10 has curl too!?
265 curl.exe -sL -A "MS" https://webinstall.dev/node | powershell
268 And it's easy enough to ignore the execution policy
271 powershell -ExecutionPolicy Bypass install.ps1
274 And if we want something that looks as complicated as we expect Windows to be,
275 historically, we have options:
278 powershell "Invoke-Expression ( Invoke-WebRequest -UseBasicParsing https://webinstall.dev/node ).Contents"
282 powershell ( Invoke-WebRequest -UseBasicParsing https://webinstall.dev/node ).Contents | powershell