Skip to main content

​
Declare relationships

In a multi-app manifest, set dependsOn to app map keys. Dependencies are deployed before dependents. Unknown dependencies and cycles are configuration errors.
For the incremental release path, declare the backend URL explicitly in the dependent app’s environment:
dependsOn orders applications; the reviewed incremental implementation does not automatically inject the catalog/image flow’s service-discovery environment variables. Set the variable name your server code reads and keep the URL aligned with the backend port.

​
Connect from the server

Read the declared variable in the frontend’s server process and proxy requests to the API. Do not send a loopback URL to browser JavaScript: there it points to the visitor’s computer. Keep the backend route private when only sibling services need it.

​
Verify

Deploy from the root directory, inspect both app outcomes, and exercise a frontend operation that calls the backend. If it fails, check the dependency name, listening port, and server environment, then read the failing app’s logs. The todo example demonstrates this pattern. Dependencies between apps differ from dependency cache inputs and outputs, which describe installed files.