-# @webinstall/packages
+# [webi-installers](https://github.com/webinstall/webi-installers)
-> WebInstall is how developers install their tools
+> [webi](https://webinstall.dev) is how developers install their tools
+
+[](https://webinstall.dev)
+
+- no `sudo`
+- no package manager
+- no messing with system permissions
+- in short: no nonsense
```bash
curl https://webinstall.dev/webi | bash
This repository contains the primary and community-submitted packages for
[webinstall.dev](https://webinstall.dev).
-# Installer Guidelines
-
-- Should install to `$HOME/.local/opt/<package>-<version>` or `$HOME/.local/bin`
-- Should not need `sudo` (except perhaps for a one-time `setcap`, etc)
-- Examples:
- - Full Packages:
- - Node.js: <https://github.com/webinstall/packages/tree/master/node>
- - Golang: <https://github.com/webinstall/packages/tree/master/golang>
- - PostgreSQL: <https://github.com/webinstall/packages/tree/master/postgres>
- - Single-Binary Installers:
- - Caddy: <https://github.com/webinstall/packages/tree/master/caddy>
- - Ripgrep: <https://github.com/webinstall/packages/tree/master/ripgrep>
- - Gitea: <https://github.com/webinstall/packages/tree/master/gitea>
- - Convenience Scripts:
- - Prettier: <https://github.com/webinstall/packages/tree/master/prettier>
- - Rust-lang: <https://github.com/webinstall/packages/tree/master/rustlang>
- - Rust-lang:
- <https://github.com/webinstall/packages/tree/master/vim-sensible>
-
-# How it works
+# How webi works
- Contacts official release APIs for download URLs
- Selects the appropriate package version and archive format
-- Installs to `$HOME/.local/`
+- Installs to `$HOME/.local/opt` or `$HOME/.local/bin`, as appropriate.
- Updates `PATH` via `$HOME/.config/envman/PATH.env`
- Symlinks or copies current selected version
More technically:
1. `<package>/releases.js` transforms the package's release API into a common
- formatt
+ format
- (i.e. HTML, CSV, TAB, or JSON into a specific JSON format)
- common release APIs are in `_common/` (i.e. `_common/github.js`)
2. `_webi/bootstrap.sh` is a template that exchanges system information for a
`https://webinstall.dev/api/installers/<pkg>@<ver>.sh?formats=zip,tar`
- `bash install-<pkg>.sh` => download, unpack, move, link, update PATH
+# Philosophy (for package authors / maintainers publishing with webi)
+
+- Should install to `$HOME/.local/opt/<package>-<version>` or `$HOME/.local/bin`
+- Should not need `sudo` (except perhaps for a one-time `setcap`, etc)
+- Examples:
+ - Full Packages:
+ - Node.js: <https://github.com/webinstall/packages/tree/master/node>
+ - Golang: <https://github.com/webinstall/packages/tree/master/golang>
+ - PostgreSQL: <https://github.com/webinstall/packages/tree/master/postgres>
+ - Single-Binary Installers:
+ - Caddy: <https://github.com/webinstall/packages/tree/master/caddy>
+ - Ripgrep: <https://github.com/webinstall/packages/tree/master/ripgrep>
+ - Gitea: <https://github.com/webinstall/packages/tree/master/gitea>
+ - Convenience Scripts:
+ - Prettier: <https://github.com/webinstall/packages/tree/master/prettier>
+ - Rust-lang: <https://github.com/webinstall/packages/tree/master/rustlang>
+ - vim-sensible:
+ <https://github.com/webinstall/packages/tree/master/vim-sensible>
+
## Creating an Installer
An install consists of 5 parts in 4 files:
my-new-package/
- README.md (package info in frontmatter)
- releases.js
- - install.sh
- - install.bat
+ - install.sh (bash)
+ - install.ps1 (PowerShell)
```
1. Create Description
These variables will be set by the server:
-```
+```bash
WEBI_PKG=example@v1
-WEBI_NAME=example
WEBI_TAG=v1
WEBI_HOST=https://webinstall.dev
WEBI_RELEASES=https://webinstall.dev/api/releases/example@v1?os=macos&arch=amd64&pretty=true
WEBI_PKG_FILE=example-macos-amd64.tar.gz
```
+```bash
+PKG_NAME=example
+PKG_OSES=macos,linux,windows
+PKG_ARCHES=amd64,arm64,x86
+PKG_FORMATS=zip,xz
+```
+
```bash
WEBI_TMP=${WEBI_TMP:-"$(mktemp -d -t webinstall-foobar.XXXXXXXX)"}
WEBI_SINGLE=""
```bash
webi_check # Checks to see if the selected version is already installed (and re-links if so)
-webi_download # Downloads the selected release to $HOME/Downloads/<package-name>.tar.gz
+webi_download # Downloads the selected release to $HOME/Downloads/
webi/<package-name>.tar.gz
webi_extract # Extracts the download to /tmp/<package-name>-<random>/
webi_path_add /new/path # Adds /new/path to PATH for bash, zsh, and fish
webi_pre_install # Runs webi_check, webi_download, and webi_extract
webi_install # Moves extracted files from $WEBI_TMP to $pkg_src
webi_link # replaces any existing symlink with the currently selected version
-webi_post_install # Runs `webi_add_path $pkg_dst_bin`
+webi_post_install # Runs `webi_path_add $pkg_dst_bin`
```
# Roadmap
- Wrap release APIs to unify and expose
+- [ ] Support more Windows packages
- [ ] Support arbitrary git urls (i.e. `@github.com/node/node`)
- (maybe `ghi node/node` for github specifically)
- [ ] Support git as an archive format
+
+<!--
+
+# Windows Notes
+
+```bat
+set WEBI_HOST=https://webinstall.dev
+```
+
+Windows 10 has curl too!?
+
+```bat
+curl.exe -sL -A "MS" https://webinstall.dev/node | powershell
+```
+
+And it's easy enough to ignore the execution policy
+
+```bat
+powershell -ExecutionPolicy Bypass install.ps1
+```
+
+And if we want something that looks as complicated as we expect Windows to be,
+historically, we have options:
+
+```bat
+powershell "Invoke-Expression ( Invoke-WebRequest -UseBasicParsing https://webinstall.dev/node ).Contents"
+```
+
+```bat
+powershell ( Invoke-WebRequest -UseBasicParsing https://webinstall.dev/node ).Contents | powershell
+```
+
+-->
projects / webi-installers / .git / blobdiff