PastureStack Web Console

Web Console is the browser interface for environments, hosts, stacks, services, containers, catalogs, storage, networking, access control, and administration.

PastureStack is an independent community effort to preserve and modernize the Rancher 1.6 ecosystem. It is not affiliated with Rancher Labs or SUSE. This fork of rancher/ui preserves upstream history, authorship, licenses, and dependency notices.

Current release

Web Console 1.6.180 is published, fixing all-time audit listing, polling and JSON/XLSX export queries. This contract requires the matching Server v1.6.518 broker. The console archive is published independently of Server assembly.

For component identities, checksums, focused tests, and known verification limits, see the current release note. Historical changes are in release notes, not this quick-start guide. Use the Server installation guide for deployment; the console archive alone is not a control plane.

Features and operator guides

• Role-aware navigation and resource actions use API schema capabilities; the backend remains the authorization authority.
• Resources and hardware: shared memory, runtimes, GPU/graphics devices, and advanced container limits. Options require compatible API/agent versions and host capabilities; device visibility is not exclusive GPU allocation.
• OpenID Connect: provider configuration, stable identity assignment, provider switching, and local recovery.
• Multi-factor authentication: TOTP, passkeys, recovery codes, account recovery, and administrator controls.
• Console workspace: movable terminal, log, and VM console windows. Live entries can reconnect; ended entries do not reopen through late callbacks or remounts. Open a new entry explicitly after ending a session.
• Operator-selected storage removal: selection, preview, confirmation, and bounded concurrent removal.

Catalog translations use optional io.pasturestack.catalog.name.<locale> and io.pasturestack.catalog.description.<locale> labels. Unknown locales and third-party catalogs fall back to canonical metadata.

Build and test

Use the supported toolchain in COMPATIBILITY.md:

npm ci --ignore-scripts
npm run build -- --environment=production
npm test
package_version=$(node -p 'require("./package.json").version')
bash scripts/package-static-candidate \
  "$package_version" dist "build/ui/${package_version}.tar.gz"

Packaging uses the current Git commit timestamp, or an explicit SOURCE_DATE_EPOCH, and emits a deterministic archive plus portable SHA-256 checksum. The archive root and VERSION.txt must match the numeric package version. This creates a candidate; publication is a separate reviewed step.

Component tests, artifact verification, and real-host/browser acceptance are separate evidence. Do not infer full resource/role/hardware coverage from a successful build. See SECURITY.md and ORIGIN.md for security boundaries and provenance.

License and attribution

The inherited project uses Apache License 2.0, with attribution in COPYRIGHT_DETAILS.md. Bundled dependencies retain their own licenses and notices. Contributors claim authorship only for their changes.