Engineering
BoxerlRenovierer - Managed Container Updates for Dotnet Aspire
Last week, I gave a talk about .NET Aspire at the .NET meetup in Linz.
Drawback of Aspire
One of the drawbacks of Aspire that I mentioned there is that it does not yet support automatic updates, as provided by Renovate, for example.
However, on the way to the meetup, I had an idea on how to link the support of docker-compose in Renovate with Aspire to utilize these capabilities.
Introducing BoxerlRenovierer
No sooner said than done - implemented over the weekend.
Now there is a first pre-release.
- Add a reference to
BoxerlRenovierer
- Add
compose.yml
to Aspire Apphost - Add one line of code
Then BoxerlRenovierer is set up and ensures that Aspire uses your compose.yml
as the source for container versions.
This means that Aspire will use the container specified in the compose.yml
(including version and container hash) instead of the one specified in Aspire.
Advantage: Everyone works with exactly the same version of the container, even in Aspire. And Renovate automatically manages the updates of the containers.