Tracking issue - Multi-app run enhancements

[mukundansundar]

Describe the proposal

• Add support for Windows for dapr multi-app run #1220
• Add Windows support for dapr stop -f #1221
• dapr list display the paths to the application and daprd logs in multi-app run #1228
• [Proposal] Add root name property to run file #1204
• Enhance run configuration file to have a depends_on field for apps #1144
• Enhance dapr run to store logs temporarily for any run call #1145
• Enhance dapr logs to view logs in self hosted mode  #1146
• Enhance dapr run to have a detached mode #1147
• [Proposal] Add metadata field for applications in Dapr Compose configuration file  #1154
• [Proposal] Add ability to override application commands in Dapr Compose configuration files #1155

Release Note

RELEASE NOTE:

[mcrio]

Hi @mukundansundar I wasn't aware of this topic so copying my comment from another one which is closed in favor of this one:

First I would like to thank the contributor for providing this feature :)

Use case: Start multiple .net based services and their Dapr sidecars during development. Previously I used Tye (no longer maintained).

What I like so far:

• Faster startup time compared to Tye
• Easy Yaml config

What I am having some difficulties with:

• After running dapr run in case some service fails to start that is not indicated in the CLI output.
• Logs have a hard coded path, namely the projects .dapr/logs subdirectory.
• It's not very easy to hunt for the logs in different folders and files, especially as each run generates new files.