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.239 loads the AWS SDK for JavaScript v3 when the Amazon EC2 host wizard connects. The optional Bridge 0.2.37 is compatible with this console.
The full nameless-Host lookup fix requires the published Engine 0.183.395, included in Server 1.6.597. The existing wire protocol remains compatible with Engine 0.183.391 or a qualified compatible assembly. Registry Key scopes require Engine 0.183.394; current Stack rollback uses Compose 0.14.45. Deploy through the Server guide.
See the release note for the EC2 tags fix.
Browser users can review switching to a visible environment or setting their own default environment. Both require a human confirmation in the console. See the environment workflow.
Typed Stack finish-upgrade, cancellation and rollback use the existing native owners and separately reviewed plans. Cancellation proves the parent checkpoint; child work must be checked separately. Rollback restores only currently eligible service upgrades. Matching Server deployment and native acceptance remain separate from component publication.
- Experimental AI collaboration: twelve typed tools for resource discovery, conditional descriptions and server-owned lifecycle plans. Disabled by default. Includes human review controls and an optional dedicated-Key stdio bridge; native browser tools require a supported secure-context browser.
- 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.
The twelve shared tools use opaque references and fresh native role, membership, schema and API Key checks. Supported families remain partial. Plans require human review and durable completion receipts; client reports do not establish authorization or business success. The Engine's four independent AI flags remain default-off, and each Web Console page starts with browser tools off.
Ordinary metadata views exclude credentials, Certificate PEM material, private
audit payloads and raw process logs. The explicit container_logs view returns
bounded application text under native LOGS authority and live Key/session
ceilings. That text is untrusted and may contain application secrets; audit
retains metadata only. Process reads use the native global owner; Project
ownership grants no global process access. Select apiKeyRestricted explicitly
for restricted-Key discovery and audit; the default searches ordinary apiKey
only. Key policy details describe configured policy, not effective grants.
The optional get_resource({resourceRef, view: "stack_graph"}) reads bounded
ordinary-Service links. Completeness remains unknown; ordinary detail performs
no graph query without the selector. Empty or unavailable Host, Volume and
process results do not establish unused resources, safe removal or completeness.
Container creation verifies stopped configuration, including supported native port mappings; a live port binding requires a separate approved start. Typed TCP load-balancer creation requires explicit activation and complete ordered rules. Load-balancer metadata changes do not edit listeners, backends, certificates, scale or lifecycle. Certificate material and advanced configuration remain in the normal human interface. Native workflow acceptance is documented separately in the release notes.
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.
Machine driver cards display each driver's API name, including drivers that share the generic icon. Catalog driver cards retain localized catalog names.
The Archive switch before stack sorting includes archived stacks and services; it is off by default and remembers each user's choice separately for each environment. Hidden counts do not replace actual resource totals. Direct detail links remain available, with an archived badge and Restore in the existing menu.
Archiving requires a compatible server, the resource's existing update capability,
and completely stopped services and containers. System and infrastructure
resources cannot be archived. Archive only changes the persisted archived flag:
it does not stop, delete, or recreate anything. Mounted directories and volumes
remain; back up their source data yourself before moving hosts or deleting mount
sources. Restore the resource and its parent stack before starting it or adding
services. Restoring a stack preserves independently archived child services.
Use the supported toolchain in COMPATIBILITY.md:
npm ci --ignore-scripts
node scripts/apply-minimatch-security-backport.cjs
npm run build -- --environment=production
npm testThe explicit source-build step applies the pinned upstream minimatch security fix while retaining the API required by this Ember toolchain. Build, test and development-server entries verify those bytes before loading build plugins. Repeat the step after reinstalling dependencies; a missing or altered backport fails with a diagnostic instead of silently running an unpatched build. See the backport provenance.
To produce a release candidate with Docker, use the same isolated producer as CI. It installs the frozen application and schema-verifier dependencies, captures final module/file evidence, packages twice, verifies both SBOM sets and writes the release sidecars to a dedicated output directory:
export GITHUB_SHA=$(git rev-parse HEAD)
export SOURCE_DATE_EPOCH=$(git show -s --format=%ct "$GITHUB_SHA")
export VALIDATION_SCOPE=sbom
export WEBMCP_MODE=off
release_dir=$(mktemp -d)
bash scripts/build-ui-release-candidate "$release_dir"The archive root and VERSION.txt match the numeric package version. Runtime
inventory is checked against the packaged tree, including packaging exclusions,
rather than the raw Ember output. This command creates a candidate; publication
is a separate reviewed step. See SBOM boundaries.
WEBMCP_MODE is the AI collaboration capability ceiling (off, read-only,
or enabled); the producer and workflow default to off. Select enabled
explicitly to include the full collaboration panel and tools. Every new page
still starts with browser tools off, until the user opts in through that panel.
The archive's webmcp-build.json and matching *-webmcp.json release sidecar
record the ceiling and fixed initialMode: off; their bytes are covered by the
archive/manifest and sidecar checksums. Publish one selected profile per version.
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.