UFO-RUNJSON(1)

πŸ’– NAME πŸ’–

ufo-runjson β€” the girl who runs your UFO workflows when they're written as JSON. bestie literally just hands her a JSON file and she makes the workflow go. that's the entire job description, and she's obsessed with it. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

ufo-runjson [-t] [-a] [-s dynamic|fixed] [-v] FILE.json

🌸 DESCRIPTION 🌸

okay so here's the tea: ufo-runjson takes the workflow that's defined inside FILE.json and executes it. that's it. that's the whole vibe. you bring the JSON, she brings the execution. no cap. ✨


πŸ’… OPTIONS πŸ’…

  • --trace, -t β€” turns on execution profiles output, and those profiles are the kind you can analyse with ufo-prof. so like, receipts for your run. πŸ“Š
  • --address, -a β€” the host address of one or more ufod instances. yes bestie, more than one is allowed, she's flexible like that. 🫢
  • --scheduler, -s β€” lets you pick a scheduler that is not the default dynamic scheduler. you got options, use them. πŸ’…
  • --version β€” spits out the version number. that's it, that's the whole thing. ⭐
reminder bestie: in the synopsis you'll see -v hanging out with --version, and the scheduler choices are written exactly as dynamic|fixed. keep them exactly like that, fr fr. πŸ™ˆ

mwah πŸ’‹ this little page is dated 05/10/2025 and comes to you straight from the UFO-RUNJSON(1) corner of the manual β€” same title, same everything, just with way more sparkle. now go run a workflow, you icon. πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from