Distributed mutex provider ovveride

[k-u-s]

Is your feature request related to a problem? Please describe.
When debugging i often terminate process that causes mutex to not dispose correctly and therefor next run is blocked.

Describe the solution you'd like
Allow to specify to skip mutex distributed lock instead via cmd args for eg: --distributed-mutex-provider none
Also that has advantage over alternative solution described bellow that allows to be run on machines that do not have access to internet and servicestack services.

Describe alternatives you've considered
Running scripts on before start that changes token to new value every time.

Additional context
Not available

[peters]

I think the solution of a random token each time is an acceptable workaround. Are you unable to connect to snapx.dev ?

[k-u-s]

From what I understand that script just builds and starts project. I do not have problem with building or starting it.

Problem is that after I terminate process it block on acquiring mutex. Which normally is fine just in my setup its inconvenient.

Also on CI it is pretty annoying to setup when outgoing traffic is not allowed

[DrMaester]

We are unable to connect to snapx.dev because of our proxy setup. Therefore we would be very interested in overriding the distributed mutex provider. Or is there an workaround to use snapx without internet connection ?