Skip to content

docs(readme): link the provisioning recording #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
github-actions merged 1 commit into from
Oct 6, 2026
Merged

docs(readme): link the provisioning recording #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,11 @@ Reached as `http://localhost`, which is a browser **secure context** (clipboard
+ WebAuthn work) with no certificate warning; HTTPS is opt-in for non-localhost
access.

To see what a commissioned cluster does next, an 81-second recording of one
media workload being provisioned through the console, with a plain account of
what it does and does not show, is on the
[organization page](https://github.com/dmfdeploy).

> **What you get (the deliverable):** a **commissioned, verified cluster** plus
> one or more **passphrase-wrapped encrypted backups** (browser downloads). The
> container is **disposable / run-once** — delete it when you're done and the
Expand Down
Loading