Gerardo Grignoli

Results 154 comments of Gerardo Grignoli

What if we create a `ddevfixhosts.ps1` powershell file? - ddev shall just run `powershell.exe -File ddevfixhosts.ps1 /some/file/with/current/status` ( check this out ![image](https://github.com/ddev/ddev/assets/3901474/3eb0fd5d-2cdd-4a86-9e93-d8b3e9d9248a)

> So at this point, we'd just run PowerShell.exe -Verb runas -FilePath ddev.exe -ArgumentList 'hostname', domain-name-to-add.ddev.site` or something like that. yes that could work too, instead of a powershell script,...

> Just starting the convo...I also assume Windows is using the same techniques as gsudo? I wonder if there are any exposed APIs that could be leveraged in gsudo? Microsoft...

I added a config setting, that when toggled will ensure gsudo path appears first in the PATH in #353. It's currently named `PathPrecedence` ![image](https://github.com/gerardog/gsudo/assets/3901474/03297a83-9ffc-4d61-bb0a-a85d396ac9d8) Alternatively, I could name the config...

Pre-Release available: https://github.com/gerardog/gsudo/releases/tag/v2.5.0

v2.5.0 is out. Anything else to address, or any other idea?

Yeap. I lack the skills to make a beautiful one... For https://gerardog.github.io/gsudo/ I did this thing: ![image](https://github.com/gerardog/gsudo/assets/3901474/3a5fa950-72db-4ec8-ae93-430aa24d4e2f) ... which is terrible ... suggestions accepted!

Given that constraint, (and others, like `SHELLEXECUTEINFO.lpDirectory` being replaced to `System32` when `Verb=RunAs`) I would then suggest you to elevate `cmd /c cd %folder% & %command%` to workaround those limitations....

For some reason, ShellExecuteEx with Verb=RunAs respects the starting directory if it is elevating dotnet apps but not for other types... (eg. `sudo -N Pwsh.exe` works but `sudo -N PowerShell.exe`...