NUKE VS CliWrap

Is it similar to Nuke?

Another thing I could recommend is to use something like Nuke build system to automate more complex tasks that aren't good fit for csproj using C# code (for example - publishing and zipping self-contained release of some service for specific platform using current date and time or commit hash as version number).

testcontainers and https://github.com/dotnet/Docker.DotNet are on my to-do list to try out, but just like with something like https://nuke.build/ i can't see the value other than that the config would be c# instead of some flavour of yaml.

We started using https://nuke.build/. Early days so can’t comment too much but it seems good so far.

I think you're giving a really bad example of what consumers should expect from open-source projects. This year I reworked the whole website, released several versions, did a huge chunk of development, and spoke at 5 events (with travel). This is the first significant gap in almost 6 years of continuous development. Maybe it's hard to imagine, but also maintainers sometimes face severe issues in their life. Comments like this don't make it any better.

Posting this here because I think only .NET people use Nuke (https://nuke.build/) to manage their build.

We will use the command docker logs --follow CONTAINER-NAME-OR-ID to retrieve the logs of the external container. To facilitate the execution of the external docker process, we will use CliWrap instead of the primitive Process.

That being said, keep up the good work. I see a lot of potential in combo with libs like https://github.com/Tyrrrz/CliWrap

Check out CliWrap. https://github.com/Tyrrrz/CliWrap

I am using CliWrap to create my own wrapper for the functionality I need from FFmpeg. Works pretty well!

https://github.com/Tyrrrz/CliWrap

Take a look at https://github.com/Tyrrrz/CliWrap for calling another process from one process.

For example, using the great Cli.Wrap library:

We can use Verify to perform snapshot testing and check for the correct output of the program. In order to make things easier and simplify working with process output capturing and invocation, I used CliWrap.

> You can take a look at System.Diagnostics.Process for one of the worst offenders.

Yeah, this is one of my least favourite APIs in all of .NET. My understanding is that the .NET team is planning to redo it in the next few years, but if you want something better right now I highly recommend the excellent CliWrap library: https://github.com/Tyrrrz/CliWrap