Skip to main content
Run fluid portal <command> --help for the exact options installed in your project.

Identify a definition

pull and clone can select by name or ID. Prefer --id when names repeat.

Separate local, draft, and live effects

  • dev and doctor are local checks.
  • pull reads remote draft state.
  • push writes remote draft state.
  • version create makes an immutable snapshot.
  • version activate changes the live definition.
Portal Definition commands do not publish Widget Packages. Company Widget Packages use fluid portal widget create and fluid portal deploy; see the company package quickstart.

Push without prompts

To push and make the result live in one non-interactive step, run:
  • --yes skips the confirmation prompt.
  • --activate creates a version and activates it, but only after every push phase succeeds. A partial push exits with a non-zero code and stays in the working definition. Nothing goes live.
  • -m, --message <message> adds a message to the push.
--yes never approves widget capabilities. When a changed screen places a widget that newly asks for a capability, an interactive push lists the widgets and asks you to approve them. A non-interactive push stops with this error:
Review the listed packages, then rerun the same push with one of these flags: Add a flag only after someone has reviewed the packages it approves. See Network access.