Replies: 1 comment 1 reply
-
|
I've though about this, but never really figured out a good way to implement it. This sounds lika a great way though. Are you interested in implementing a feature like this? Note that pup supports similar shell operators as deno task shell, so some dependency logic could be carried out simply using &&, || and so on. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! I'm considering using pup for a rather large project (~ 20 services), but a few features are currently lacking. One of the most important addition to pup before making the switch is the possibility to declare dependencies:
{ "processes": [ { "id": "api", "cmd": "yarn workspace api run dev" }, { "id": "frontend", "cmd": "yarn workspace frontend run dev", "dependsOn": ["api"] } ] }With this config file, running
pup start frontendwould runapifirst.Later on, if Pup features a healthcheck, the
dependsOnfield could be extended with features similar to docker compose #depends_on:{ "id": "frontend", "dependsOn": { "api": { "condition": "healthy", "restart": false } } }Beta Was this translation helpful? Give feedback.
All reactions