@xgent-ai/skills 0.1.0 → 0.3.0

package/skills/working-with-mise/references/dev-tools/backends/pypi-html.md

@@ -0,0 +1,331 @@
+PyPI Backend
+
+PyPI Backend [​](#pypi-backend)
+
+The `pypi` backend installs Python command-line applications in isolated virtual environments. Each tool gets its own dependencies. Use a project environment and pip or uv for application libraries such as NumPy and requests.
+
+## Quick start [​](#dependencies)
+
+Install uv, Python, and a CLI from PyPI:
+
+sh
+
+```
+mise use python@3.14 uv pypi:black
+mise exec -- black --version
+```
+
+### Project configuration [​](#usage)
+
+This adds the following to `mise.toml`:
+
+toml
+
+```
+[tools]
+python = "3.14"
+uv = "latest"
+"pypi:black" = "latest"
+```
+
+Add `-g` to `mise use` to install tools globally.
+
+mise uses uv to install tools. With [dependency locking](#dependency-locking), it runs `uv sync --frozen`; version-only installs use `uv tool install`. If uv is unavailable, version-only installs fall back to `pipx install`. See [Using pipx](#using-pipx) to select that installer explicitly.
+
+## Package sources [​](#supported-pipx-syntax)
+
+Use `pypi:black` for the PyPI distribution or `pypi:psf/black` for its GitHub source. Their releases and installation requirements can differ.
+
+| Source | Example |
+| --- | --- |
+| PyPI, latest version | `pypi:black` |
+| PyPI, specific version | `pypi:black@24.3.0` |
+| GitHub, default branch | `pypi:psf/black` |
+| GitHub, specific release | `pypi:psf/black@24.3.0` |
+| Git repository | `pypi:git+https://github.com/psf/black.git` |
+| Git branch | `pypi:git+https://github.com/psf/black.git@main` |
+
+For GitHub sources, `latest` installs from the unpinned default branch; it does not select the latest published release. Use an explicit version to select a release. For other Git URLs, `latest` resolves default-branch HEAD to a concrete commit. Remote tags are also available for explicit version requests.
+
+Direct HTTPS archive URLs are unsupported. Other source syntax may work but is unsupported and untested.
+
+## Dependency locking [​](#dependency-locking)
+
+With **uv 0.12.10 or newer**, new `mise.lock` files record the full Python dependency graph, including wheel hashes and Python/platform markers. Locked installs reuse that graph without resolving dependencies again.
+
+Create a lockfile, or upgrade an existing version-only lockfile, then install:
+
+sh
+
+```
+mise lock --upgrade
+mise install --locked
+```
+
+Commit both `mise.lock` and its [dependency sidecar directory](https://mise.jdx.dev/dev-tools/mise-lock.html#native-dependency-sidecars), which contains the native `pyproject.toml` and `uv.lock` files. Existing lockfiles keep version-only behavior until explicitly upgraded.
+
+### Updating dependencies [​](#updating-dependencies)
+
+Ordinary `mise lock` reuses the recorded graph. To refresh a tool's transitive dependencies even when its own version has not changed:
+
+sh
+
+```
+mise lock --bump pypi:black
+```
+
+You can also inspect or edit a sidecar with uv. For a tool locked to Black 24.10.0 in the default sidecar layout:
+
+sh
+
+```
+uv tree --project .mise/locks/pypi-black/24.10.0
+uv lock --project .mise/locks/pypi-black/24.10.0 --upgrade-package click
+mise lock
+```
+
+Run `mise lock` after editing a sidecar to accept its updated digest before using `mise install --locked`.
+
+### Requirements and limitations [​](#requirements-and-limitations)
+
+- **Wheels only for dependency graphs:** every dependency needs a published wheel for the target Python version and platform. Explicit `mise lock` and locked installs do not build source distributions. An ordinary `mise install` falls back to a version-only uv installation when it cannot produce a wheel-only graph.
+- **PyPI packages with uv:** Git sources and standalone pipx installs use version-only locking. pipx cannot replay a uv dependency graph.
+- **No free-form installer arguments in dependency graphs:** `uvx_args` and `pipx_args` use version-only installation during ordinary installs. Explicit dependency locking rejects them because mise cannot safely translate arbitrary installer arguments into a reproducible graph. Use the semantic options instead when dependency locking is required: [`with`](#with) injects additional requirements into the tool environment, [`expose`](#expose) also exposes their executables, and [`dependency_prereleases`](#dependency_prereleases) sets uv's prerelease policy. These are locked together with the tool, so the graph covers the injected packages. Configure [Python](#choosing-python) and the [registry URL](#registry-url) directly as well.
+- **Installed Python required:** lock generation needs an interpreter discoverable by uv, though it need not match the tool's configured Python version. Graph installs use the selected mise Python and do not download a replacement.
+- **Complete lockfiles required:** revision-2 locked uv installs fail if their dependency graph is missing. Run `mise lock` to generate it.
+
+The graph covers the Python range that every locked requirement supports, starting at Python 3.8, and retains all published wheel targets for portability. Requirements injected with [`with`](#with) or [`expose`](#expose) are part of that calculation: one pinned to an exact version raises the range's floor to the release's own `requires-python`, because a single release cannot span the wider range the way uv resolves an unpinned requirement. A pin carrying an environment marker that tests the interpreter, such as `python_version < "3.12"`, is left out, since it is simply absent from the versions it excludes. This can make sidecars large. Frozen installs reuse uv's artifact cache.
+
+Different dependency graphs and configured Python interpreters get separate installations; `mise ls` still shows the package version. For system Python, mise records the interpreter's implementation, major/minor version, ABI, and platform during installation so later commands can find the environment even if that interpreter is no longer on PATH.
+
+### Private indexes and release age [​](#private-indexes-and-release-age)
+
+Simple-only indexes must provide consistent `data-requires-python` metadata on the selected release's wheel links. Registry credentials belong in the installer environment or credential provider. URLs containing credentials or query strings cannot be recorded in the lockfile.
+
+[`minimum_release_age`](https://mise.jdx.dev/configuration/settings.html#minimum_release_age) filters transitive dependencies when resolving a graph, not when replaying it. For version-only installs, mise passes uv's `--exclude-newer` flag (requires uv 0.2.22 or newer) or pip's `--uploaded-prior-to` flag through pipx.
+
+## Choosing Python [​](#choosing-python)
+
+For graph-locked tools, configure the interpreter through mise:
+
+toml
+
+```
+[tools]
+python = "3.14"
+uv = "0.12.10"
+"pypi:black" = "latest"
+```
+
+For legacy version-only installs, the selected installer chooses the interpreter; `uvx_args` and `pipx_args` can pass installer-specific Python options.
+
+## Python upgrades [​](#python-upgrades)
+
+If a CLI stops working after changing Python, reinstall it under the intended Python version. This recreates the tool environment and its dependencies:
+
+sh
+
+```
+mise install --force pypi:black
+mise exec -- black --version
+```
+
+Check which Python version is active before reinstalling. Existing virtualenvs and native extensions do not necessarily remain usable after their interpreter is removed or changed.
+
+## Using pipx [​](#using-pipx)
+
+To use the pipx installer, install Python and pipx, then disable uv for the tool:
+
+sh
+
+```
+mise use python@3.14 pipx
+```
+
+toml
+
+```
+[tools]
+"pypi:ansible" = { version = "latest", uvx = false, expose = [], pipx_args = "--include-deps" }
+```
+
+This uses version-only locking. An existing uv dependency graph cannot be replayed with pipx.
+
+### Compatibility with `pipx:` [​](#compatibility-with-pipx)
+
+The `pipx:` backend name remains supported. Existing configurations do not need to change. However, `pypi:black` and `pipx:black` are distinct tool identities: switching prefixes creates a separate installation and lock entry. mise preserves explicit `pipx:` names in output and lockfiles.
+
+The legacy option names `uvx` and `uvx_args` control uv installation; they do not mean mise runs the `uvx` command.
+
+## Settings [​](#settings)
+
+Set these with `mise settings set [VARIABLE]=[VALUE]` or by setting the environment variable listed.
+
+### `pypi.registry_url`[](#pypi.registry_url)
+
+- Type: `string`(optional)
+- Env: `MISE_PYPI_REGISTRY_URL`
+- Default: `None`
+
+Package registry URL for Python tools (pipx.registry\_url is a compatibility alias).
+
+### `pypi.uvx`[](#pypi.uvx)
+
+- Type: `boolean`(optional)
+- Env: `MISE_PYPI_UVX`
+- Default: `None`
+
+Use uv for Python tools when available (pipx.uvx is a compatibility alias).
+
+## Tool Options [​](#tool-options)
+
+The following [tool-options](https://mise.jdx.dev/dev-tools/#tool-options) are available for the `pypi` backend—these go in `[tools]` in `mise.toml`.
+
+### `registry_url` [​](#registry-url)
+
+Set the registry URL used to resolve versions for this tool. Include a `{}` placeholder for the package name. This overrides the `pypi.registry_url` setting for this tool.
+
+toml
+
+```
+[tools]
+"pypi:my-tool" = { version = "latest", registry_url = "https://packages.example.com/pypi/{}/json" }
+```
+
+Dependency locking also derives the install index from this URL. For version-only installs, configure the install index separately through `uvx_args` or `pipx_args`. For example, with the pipx installer:
+
+toml
+
+```
+[tools]
+"pypi:my-tool" = { version = "latest", uvx = false, registry_url = "https://packages.example.com/pypi/{}/json", pipx_args = "--pip-args='--index-url https://packages.example.com/pypi/simple'" }
+```
+
+### `install_env` [​](#install-env)
+
+Set environment variables for the installer. mise still sets the tool directory, bin directory, and configured Python package index variables after applying `install_env`. For the uv installer, for example:
+
+toml
+
+```
+[tools]
+"pypi:black" = { version = "latest", install_env = { UV_COMPILE_BYTECODE = "1" } }
+```
+
+### `extras` [​](#extras)
+
+Install optional dependencies (Python package extras).
+
+toml
+
+```
+[tools]
+"pypi:harlequin" = { version = "latest", extras = "postgres,s3" }
+# equivalent array form:
+# "pypi:harlequin" = { version = "latest", extras = ["postgres", "s3"] }
+# extras also work with Git sources:
+# "pypi:psf/black" = { version = "latest", extras = ["jupyter"] }
+```
+
+When passing extras inline, use mise's `key=value` tool-option syntax:
+
+bash
+
+```
+mise use 'pypi:psf/black[extras=jupyter]@latest'
+```
+
+For Git repositories whose name differs from the Python distribution name, set `package_name` so mise can build the requirement used to select extras:
+
+toml
+
+```
+[tools]
+"pypi:owner/repository" = { version = "latest", package_name = "distribution", extras = ["feature"] }
+```
+
+### `pipx_args` [​](#pipx-args)
+
+Additional arguments for `pipx install`. These apply only to version-only installs using pipx and are unsupported with dependency graphs.
+
+toml
+
+```
+[tools]
+"pypi:ansible" = { version = "latest", uvx = false, expose = [], pipx_args = "--include-deps" }
+```
+
+### `with` [​](#with)
+
+Install additional Python requirements in the tool environment. This option requires uv and participates in dependency locking.
+
+toml
+
+```
+[tools]
+"pypi:azure-cli" = { version = "latest", with = ["pip"] }
+```
+
+A requirement pinned to an exact version narrows the locked Python range to the versions that release supports, so the tool may end up needing a newer interpreter than it declares on its own. Guard the pin with an interpreter marker, such as `"legacy==1.0.0; python_version < '3.12'"`, to keep the wider range when the requirement is only needed on some versions.
+
+### `expose` [​](#expose)
+
+Install additional Python requirements and expose their executable entry points. This option requires uv 0.8.5 or newer and participates in dependency locking.
+
+toml
+
+```
+[tools]
+"pypi:ansible" = { version = "latest", expose = ["ansible-core"] }
+```
+
+### `dependency_prereleases` [​](#dependency-prereleases)
+
+Set uv's prerelease policy for dependency resolution. Supported values are `disallow`, `allow`, `if-necessary`, and `explicit`. This option requires uv and is applied both when generating dependency graphs and during version-only installs.
+
+toml
+
+```
+[tools]
+"pypi:azure-cli" = { version = "latest", dependency_prereleases = "allow" }
+```
+
+### `uvx` [​](#uvx)
+
+Set to `false` to use pipx instead of uv for this tool. This also disables dependency graph locking and requires pipx to be installed.
+
+toml
+
+```
+[tools]
+"pypi:ansible" = { version = "latest", uvx = false, expose = [] }
+```
+
+The empty `expose` list clears Ansible's uv-backed registry default. Clear any other semantic defaults the same way when overriding a registry tool to use pipx.
+
+### `uvx_args` [​](#uvx-args)
+
+Additional arguments for version-only installs using `uv tool install`. These are unsupported with dependency graphs; `pipx_args` applies only to pipx.
+
+toml
+
+```
+[tools]
+"pypi:ansible-core" = { version = "latest", uvx_args = "--resolution lowest" }
+```
+
+Prefer the semantic [`with`](#with), [`expose`](#expose), and [`dependency_prereleases`](#dependency_prereleases) options when they cover the desired behavior. Unlike arbitrary arguments, those options support dependency graphs.
+
+Implementation: [`src/backend/pipx.rs`](https://github.com/jdx/mise/blob/main/src/backend/pipx.rs).
+
+[Edit this page](https://github.com/jdx/mise/edit/main/docs/dev-tools/backends/pypi.md)
+
+Last updated:
+
+Pager
+
+[Previous pagepackslip](https://mise.jdx.dev/dev-tools/backends/packslip.html)
+
+[Next pagepkgx](https://mise.jdx.dev/dev-tools/backends/pkgx.html)
+
+MIT License·Copyright © 2026· [![](https://github.com/jdx.png?size=96)jdx.dev](https://jdx.dev)

package/skills/working-with-mise/references/dev-tools/backends/s3-html.md

@@ -0,0 +1,346 @@
+S3 Backend
+
+S3 Backend [​](#s3-backend)
+
+The `s3` backend installs binaries and archives from Amazon S3 or S3-compatible storage such as MinIO. Use it when access should follow your AWS credentials or when version discovery needs to list objects in a bucket. No AWS CLI is required.
+
+The code for this is inside of the mise repository at [`./src/backend/s3.rs`](https://github.com/jdx/mise/blob/main/src/backend/s3.rs).
+
+## Usage [​](#usage)
+
+Replace the bucket and object key below with an artifact you can read for your platform. Use a concrete version for a fixed object URL:
+
+sh
+
+```
+mise use "s3:my-tool[url=s3://my-bucket/tools/my-tool-v1.0.0.tar.gz]@1.0.0"
+```
+
+This writes the following to the project's `mise.toml`. Add `-g` for global configuration, and run `mise exec -- my-tool --version` to verify the install:
+
+toml
+
+```
+[tools]
+"s3:my-tool" = { version = "1.0.0", url = "s3://my-bucket/tools/my-tool-v1.0.0.tar.gz" }
+```
+
+## Authentication [​](#authentication)
+
+mise uses the AWS SDK's [default credential provider chain](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/credproviders.html). It supports environment credentials, shared AWS profiles, web identity, and container or instance roles. Prefer an existing profile or workload role over copying long-lived access keys into project configuration.
+
+For a configured local profile:
+
+sh
+
+```
+AWS_PROFILE=development AWS_REGION=us-east-1 mise install
+```
+
+Temporary environment credentials require `AWS_SESSION_TOKEN` as well as `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. The `region` tool option can select the bucket's region explicitly.
+
+Downloading a known object requires `s3:GetObject`. Discovery through an object prefix also requires `s3:ListBucket`; discovery through a manifest needs read access to that manifest. A successful object download does not prove that version listing is permitted.
+
+## Tool Options [​](#tool-options)
+
+The following [tool-options](https://mise.jdx.dev/dev-tools/#tool-options) are available for the `s3` backend—these go in `[tools]` in `mise.toml`.
+
+### `url` (Required) [​](#url-required)
+
+Specifies the S3 URL to download the tool from. The URL supports templating with `{{ version }}`:
+
+toml
+
+```
+[tools]
+"s3:my-tool" = { version = "1.0.0", url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz" }
+```
+
+### `endpoint` [​](#endpoint)
+
+Specify a custom S3-compatible endpoint for services like MinIO, DigitalOcean Spaces, or self-hosted S3:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+endpoint = "https://minio.example.com"
+```
+
+### `region` [​](#region)
+
+Specify the AWS region for the S3 bucket:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+region = "us-west-2"
+```
+
+### Platform-specific URLs [​](#platform-specific-urls)
+
+For tools that need different downloads per platform, use the table format:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+
+[tools."s3:my-tool".platforms]
+macos-x64 = { url = "s3://my-bucket/tools/my-tool-v1.0.0-macos-x64.tar.gz" }
+macos-arm64 = { url = "s3://my-bucket/tools/my-tool-v1.0.0-macos-arm64.tar.gz" }
+linux-x64 = { url = "s3://my-bucket/tools/my-tool-v1.0.0-linux-x64.tar.gz" }
+```
+
+### `checksum` [​](#checksum)
+
+Set the expected digest for this version and object. Replace this placeholder with a complete digest obtained from a trusted source:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0.tar.gz"
+checksum = "sha256:REPLACE_WITH_THE_64_HEX_DIGIT_DIGEST"
+```
+
+*Instead of specifying the checksum here, you can use [mise.lock](https://mise.jdx.dev/dev-tools/mise-lock.html) to manage checksums.*
+
+### `size` [​](#size)
+
+Check the expected object size in bytes. The numbers below illustrate the syntax; replace them with the actual sizes. This does not replace a checksum:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0.tar.gz"
+size = "12345678"
+```
+
+You can specify different sizes for different platforms:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+
+[tools."s3:my-tool".platforms]
+macos-arm64 = { url = "s3://my-bucket/tools/my-tool-v1.0.0-macos-arm64.tar.gz", size = "9876543" }
+linux-x64 = { url = "s3://my-bucket/tools/my-tool-v1.0.0-linux-x64.tar.gz", size = "12345678" }
+```
+
+### `strip_components` [​](#strip-components)
+
+Number of directory components to strip when extracting archives:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0.tar.gz"
+strip_components = 1
+```
+
+INFO
+
+When both `strip_components` and `bin_path` are unset, mise automatically detects when to apply `strip_components = 1`. This happens when the extracted archive contains exactly one directory at the root level and no files.
+
+### `bin` [​](#bin)
+
+Rename the downloaded binary to a specific name. This is useful when downloading a single binary object that has a platform-specific name:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-linux-x86_64"
+bin = "my-tool"
+```
+
+INFO
+
+When downloading single binaries (not archives), mise automatically removes OS/arch suffixes from the filename. For example, `my-tool-linux-x86_64` becomes `my-tool`. Use the `bin` option only when you need a specific custom name.
+
+### `rename_exe` [​](#rename-exe)
+
+Rename the executable after extraction from an archive. This is useful when the archive contains a binary with a platform-specific name that you want to rename:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0-linux.zip"
+rename_exe = "my-tool"
+```
+
+TIP
+
+Use `rename_exe` for archives where the binary inside has a different name than desired. Use `bin` for single binary downloads (not archives).
+
+### `bin_path` [​](#bin-path)
+
+Specify the directory containing binaries within the extracted archive. This disables automatic root stripping. For an archive shaped like `my-tool-VERSION/bin/my-tool`, set both options explicitly:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0.tar.gz"
+strip_components = 1
+bin_path = "bin" # after stripping an outer my-tool-VERSION directory
+```
+
+### `format` [​](#format)
+
+Explicitly specify the archive format when the URL lacks a file extension:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "1.0.0"
+url = "s3://my-bucket/tools/my-tool-v1.0.0"
+format = "tar.gz"
+```
+
+## Version Discovery [​](#version-discovery)
+
+The S3 backend supports a manifest or object listing. Configure one before using `latest`, then check it with `mise ls-remote s3:my-tool`. The examples use placeholder buckets that you must replace with your own.
+
+### Manifest File [​](#manifest-file)
+
+Fetch available versions from a JSON manifest file stored in S3:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "latest"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+version_list_url = "s3://my-bucket/tools/versions.json"
+```
+
+The manifest file can be a JSON array of version strings:
+
+json
+
+```
+["1.0.0", "1.1.0", "2.0.0"]
+```
+
+Or a JSON array of objects (use `version_json_path` to extract versions):
+
+json
+
+```
+[{ "version": "1.0.0" }, { "version": "1.1.0" }, { "version": "2.0.0" }]
+```
+
+### `version_json_path` [​](#version-json-path)
+
+Extract versions from JSON responses using a jq-like path expression:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "latest"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+version_list_url = "s3://my-bucket/tools/releases.json"
+version_json_path = ".[].version"
+```
+
+### `version_expr` [​](#version-expr)
+
+Extract versions using an [expr-lang](https://expr-lang.org/) expression for complex version extraction logic:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "latest"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+version_list_url = "s3://my-bucket/tools/versions.txt"
+version_expr = 'split(body, "\n")'
+```
+
+The expression receives the response body as the `body` variable and should return an array of version strings.
+
+### S3 Object Listing [​](#s3-object-listing)
+
+Discover versions by listing objects in the S3 bucket:
+
+toml
+
+```
+[tools."s3:my-tool"]
+version = "latest"
+url = "s3://my-bucket/tools/my-tool-v{{ version }}.tar.gz"
+version_prefix = "tools/my-tool-v"
+version_regex = 'my-tool-v(.+)\.tar\.gz$'
+```
+
+- `version_prefix`: The S3 key prefix to list objects from
+- `version_regex`: A regular expression to extract version numbers from object keys (first capturing group is used)
+
+## Custom Endpoint Example (MinIO) [​](#custom-endpoint-example-minio)
+
+Here's a complete example using MinIO as an S3-compatible backend:
+
+toml
+
+```
+[tools."s3:my-internal-tool"]
+version = "latest"
+url = "s3://tools-bucket/releases/my-tool-{{ version }}.tar.gz"
+endpoint = "https://minio.example.com"
+region = "us-east-1"
+version_list_url = "s3://tools-bucket/releases/versions.json"
+strip_components = 1 # assumes one outer directory containing bin/
+bin_path = "bin"
+```
+
+Provide the MinIO access key and secret through an AWS-compatible profile or the standard environment variables, then run `mise install`. A custom endpoint uses path-style bucket addressing; it must be reachable with a trusted TLS certificate.
+
+## Comparison with HTTP Backend [​](#comparison-with-http-backend)
+
+| Feature | S3 Backend | HTTP Backend |
+| --- | --- | --- |
+| Authentication | AWS credentials (env vars, \~/.aws/credentials, IAM) | HTTP auth headers |
+| Version discovery | S3 listing or manifest file | HTTP endpoint |
+| Custom endpoints | Yes (MinIO, etc.) | N/A |
+| Use case | AWS-authenticated object storage | Public or authenticated HTTP downloads |
+
+## Troubleshooting [​](#troubleshooting)
+
+| Error | Check |
+| --- | --- |
+| Access denied | The selected profile or role, object read permissions, and listing permissions when using `version_prefix`. |
+| Object not found | The bucket, full key, concrete version, and rendered platform URL. |
+| Signature mismatch | Credentials, session token, region, endpoint, and local clock. |
+| No versions | The manifest format or listing prefix and capture group. A download URL alone does not define a version list. |
+| Installed command missing | The archive structure after root stripping and the `bin` or `bin_path` option. |
+
+[Edit this page](https://github.com/jdx/mise/edit/main/docs/dev-tools/backends/s3.md)
+
+Last updated:
+
+Pager
+
+[Next pageGetting Started](https://mise.jdx.dev/getting-started.html)
+
+MIT License·Copyright © 2026· [![](https://github.com/jdx.png?size=96)jdx.dev](https://jdx.dev)