EVQUEUE_WFMANAGER(8)

πŸ“¦ version 2.1, in ubuntu jammy, ubuntu noble

πŸ’– EVQUEUE_WFMANAGER πŸ’–

okay bestie, welcome to section 8 of the evQueue manual β€” this one's called evqueue_wfmanager, and it's lowkey one of the most useful little tools in the whole box. let's get into it πŸŽ€


✨ NAME ✨

evqueue_wfmanager β€” evQueue utilities πŸ¦‹


🌸 SYNOPSIS 🌸

evqueue_wfmanager [ OPTIONS ] --launch <wf name> [--<parameter name> <parameter value>]*

πŸ’… DESCRIPTION πŸ’…

so this is the utility that lets you launch workflows straight from the command line, no clicking around required, we love a main character CLI moment πŸ‘‘

it can connect to the evQueue core either through TCP or through UNIX sockets β€” your choice, both are valid, both are iconic.

⚠️ bestie listen, this part is IMPORTANT: options MUST be passed before the --launch argument. like, before. no exceptions. the arguments that come after --launch are only workflow parameters. do not mix these up, i'm begging πŸ™

πŸ”₯ OPTIONS πŸ”₯

  • --connect connection_string β€” connect to the server identified by connection_string. two formats are accepted, periodt:
    • tcp socket: tcp://<hostname>[:<port>]
    • unix socket: unix://<path>
  • --user <username> β€” use this username if the daemon requires authentication 🫢
  • --password <password> β€” use this password if the daemon requires authentication πŸ”
  • --mode [synchronous|asynchronous] β€” run in synchronous or asynchronous mode. in synchronous mode the command only returns after the workflow is terminated (so it sits there, patiently, like a good friend waiting for you outside the store 😭). in asynchronous mode the command returns immediately after the workflow is launched, no waiting, we're speedrunning πŸ’¨
  • --timeout <timeout> β€” when you're running in synchronous mode, don't wait for workflow termination for more than <timeout> seconds. respect the clock bestie ⏰

⭐ EXAMPLES ⭐

evqueue_wfmanager --connect tcp://localhost:5000 --user admin --password admin --launch sleep --time 1

so what's happening here πŸ‘€ it connects to the evQueue daemon using TCP on localhost (port 5000). then it launches a workflow named "sleep" which takes one parameter, "time", whose value is "1". chef's kiss, that's the whole vibe ✨


🌈 SEE ALSO 🌈

http://www.evqueue.net/ β€” go look, it's giving documentation and community, iykyk πŸ’œ


and that's the whole page bestie, no cap, every option accounted for πŸ’– this one's from the evQueue utilities, version/date 2016-07-11, page EVQUEUE_WFMANAGER(8) β€” slay, go launch some workflows, you've got this πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from