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.
Web Console 1.6.183 is published. It restores add-host Close and Back route dispatch, preserves their external return target across driver redirects and settings refreshes, and derives host onboarding from the native capability of the actual submission path: RegistrationToken POST for Custom, Host POST for built-in/Other forms. Machine API POST alone grants neither form; Host POST alone cannot open Custom. See the release note for source/archive identities and checksums.
The shared native-click clipboard fix from 1.6.182 is retained. Eleven new unit cases and native browser control checks passed, including the first API-host setting save, real command-copy icon clicks, and Close returning to Hosts.
The console archive is published independently of Server assembly. See the Server current-release guide for its published component pairing and deployment workflow. Component publication and focused UI results do not imply complete Server or active-agent acceptance.
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.
- Role-aware navigation and resource actions use API schema capabilities; the backend remains the authorization authority.
- API Keys: capability-gated access policies, expiration, reviewed changes with platform MFA, and per-key audit. Grants remain bounded by live owner permissions; new secrets are shown once. Legacy Keys and servers without policy capability retain the existing workflow.
- 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.
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.
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.