You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you be open to a PR implementing parallel task execution?
My use case is developing a web app.
The backend and frontend are implemented in different languages with separate live-reloading infrastructure, so it makes sense to keep those in separate containers / dependency chains.
It'd be nice if a single command could run both tasks in parallel (in the example below, toast dev).
Currently one must open separate terminals and manually run two separate toast tasks.
This makes it harder to hand-off to teammates, since I can't give them a single command to start the dev environment.
One could write a little shell script to spawn two toast invocations, but then responsibilities are muddled ("I thought I was supposed to use toast to run commands, so why do we have some shell scripts?")
For my case, it'd be fine to interleave the output.
Alternatively we could also have an option to prefix each line of the output with the task name.
image: ubuntu:22.04@sha256:0f744430d9643a0ec647a4addcac14b1fbb11424be434165c15e2cc7269f70f8command_prefix: set -euo pipefailtasks:
dev:
description: Start the entire development systemdependencies:
- frontend
- backendfrontend:
description: Start the frontend builder / live-reloadercommand: | while true; do echo 'frontend...' sleep 1 donebackend:
description: Start the backend servercommand: | while true; do echo 'server...' sleep 1 done
The text was updated successfully, but these errors were encountered:
Hello, this is an interesting proposal, but it would be a significant change. See the discussion here: #405
I don't think I currently have the bandwidth to commit to reviewing a PR for this, but I welcome any discussion about it. It would be nice to have this someday!
(If you think this could be implemented fairly easily with a small-ish change, let me know—maybe I'm overestimating the work.)
Would you be open to a PR implementing parallel task execution?
My use case is developing a web app.
The backend and frontend are implemented in different languages with separate live-reloading infrastructure, so it makes sense to keep those in separate containers / dependency chains.
It'd be nice if a single command could run both tasks in parallel (in the example below,
toast dev
).Currently one must open separate terminals and manually run two separate toast tasks.
This makes it harder to hand-off to teammates, since I can't give them a single command to start the dev environment.
One could write a little shell script to spawn two toast invocations, but then responsibilities are muddled ("I thought I was supposed to use
toast
to run commands, so why do we have some shell scripts?")For my case, it'd be fine to interleave the output.
Alternatively we could also have an option to prefix each line of the output with the task name.
The text was updated successfully, but these errors were encountered: