--publish=web builds and signs a Rive project, and hosts it as a public page anyone
can open: one URL playing the built .riv. --publish on its own writes a signed .riv to disk.
Publish a page
1
Login
2
Choose a Workspace
Pages belong to a Workspace. If you aren’t a member of any Workspace, the CLI creates
a Free Workspace for you when you sign in, or when you next publish. To create another
Workspace, run
rive workspace create <name>.
You can also create a Workspace in the Rive Editor, or join an existing one.If you’re an Editor
in one Workspace, the CLI picks it for you. If you’re an Editor in several, the CLI
opens a picker to select one. To skip the question, pass the Workspace ID with
--workspace=<id>. rive workspace lists your Workspaces and their IDs.
--team=<id>, the older name for this flag, still works.3
Publish
--name=<name> if you pass one, then
pages.name once the project has published before, then the project’s name in
rive.yaml. So renaming the project does not move an existing page.pages: block into
rive.yaml. Later publishes leave it alone:
Signing and the web runtime
A published page is played by the Rive web runtime, and web runtimes refuse unsigned scripts. An unsigned build would load and then play nothing, so--publish=web always builds
the way --publish does.
The same watermark rule as --publish applies. A web publish from a project that isn’t
bound to a file counts against the Workspace that owns the page, and that Workspace’s
plan decides the watermark. See
Which Workspace counts.
Republish a page
A page is identified by its name within its Workspace. The name is lowercased into a slug (anything outsidea-z0-9 becomes a dash), and the url is that slug plus a short
random suffix minted once, when the page is created.
Publishing the same name again replaces what the url serves. The url does not change,
so a link you handed out keeps working and starts showing the new build. Publishing a
different name creates a different page at a different url.
--name=<name> on a later publish is a one-off: it publishes to that name without
changing the pages: block, so the project keeps pointing at its original page.
Publish from CI
--no-wait prints the url and exits as soon as the upload is accepted, without
waiting for the page to go live. With --quiet, stdout is two lines: the name (with
its expiry date, if it has one) and then the url.
--workspace=<id> as well, since the CLI can’t ask which Workspace to use when
stdin is not a terminal.
Publishing is rate limited per account. A run that hits the limit reports
too many publishes for now.Set how the control bar starts
A published page carries a small bar of controls for its fit, full screen, and copying its url. The bar shows for a moment and then hides to a lip at the bottom of the page.--drawer=<mode> changes how it starts:
The first time the bar opens, a tooltip over its Rive link reads “Made with Rive. Build
your own.” for a few seconds. On a page that starts with only the lip, the tooltip shows
above the lip first. On a paid plan,
--no-promo leaves the tooltip off. If your
Workspace moves to a plan without these options, its pages show the tooltip and the
bar again, until you upgrade.
Each publish sends its own settings, so pass --drawer= and --no-promo every time you
publish the page.
List published pages
List your published pages with thelist-published command.
built means the file is on disk. not published
means no page was found for the project’s pages: binding.