Based on this thread.
Related GitHub discussion in main dotnet/aspire repo.
- Standalone resource server
- Collecting external containers' logs
- Handling commands to external containers
To test the resource server, there's a sample docker compose file in the compose
directory. Either start the compose file
manually by
docker compose -f samples/compose/compose.yaml up -d
Or use the facilitator scripts (start-compose.ps1
, start-compose.sh
).
This compose file includes:
- An Aspire dashboard container
- A RabbitMQ container (as a sample of any message bus)
- A Redis container (as a sample of any key-value store)
- A MongoDB container (as a sample of any NoSQL database)
To cover most of the external workloads that teams who do not or cannot use the Aspire application model due to different stack or any other reason usually use.
To test the resource server running as a Docker container, there's a sample docker compose file in the samples/dockerfile
directory. Either build the Aspire.ResourceService image, and start the compose file
manually by
- Run (
docker-build.ps1
, ordocker-build.sh
) to build the Aspire.ResourceService image - Start the compose file:
docker compose -f samples/dockerfile/compose.yaml up -d
Or use the facilitator scripts (start-dockerfile.ps1
, start-dockerfile.sh
), which both builds the Aspire.ResourceService image and starts the compose file.
This compose file includes:
- An Aspire dashboard container
- An Aspire ResourceService container
- A RabbitMQ container (as a sample of any message bus)
- A Redis container (as a sample of any key-value store)
- A MongoDB container (as a sample of any NoSQL database)
To test the resource server running as a container in Minikube, please run one of the facilitator scripts (start-minikube.ps1
, start-minikube.sh
).
Please note that Minikube must be running in order for the scripts to work.
This sample setup includes:
- An Aspire dashboard container
- A RabbitMQ container (as a sample of any message bus)
- A Redis container (as a sample of any key-value store)
Once you've ran either of the scripts, please start the application itself through the solution. To use the Aspire dashboard, please port forward the Aspire Dashboard container so you can access it through your browser.
Feel free to contribute to this project by opening an issue or a pull request.