Project dependencies

Add depends_on to your yeeted.yaml (or ask your agent to “make this app depend on my-api”), and when you deploy, Yeeted brings the dependencies up first, including dependencies of dependencies, all the way down, as far as your plan's running-app capacity allows.

depends_on:
  - my-api
  - my-worker

flowchart TD
  shop[my-shop] --> api[my-api]
  shop --> worker[my-worker]
  api --> db[(managed postgres)]
  worker --> queuecache[(managed redis)]

The full dependency tree is visible on each service's page in the dashboard. If a dependency can't start (say you're out of capacity), the deploy tells you exactly which one and why, so you can stop something else, or switch to the Beta plan if you are on Free.