devtools-proxy icon indicating copy to clipboard operation
devtools-proxy copied to clipboard

Windows support

Open SergeyPirogov opened this issue 8 years ago • 5 comments

On my current project I need to run devtools-proxy in Windows 10. As I understand now it's impossible to do this. Am I right? If yes, do I need to write dev-tools.bat the same manner as .sh or it requires additional changed in library?

SergeyPirogov avatar Jun 06 '17 09:06 SergeyPirogov

Yes, you're right. The Proxy itself (proxy.py) is fully compatible with Windows already. The thing that is incompatible with Windows is a Chrome wrapper (chrome-wrapper.sh). I see 2 possible solutions:

  • write chrome-wrapper.bat (or .ps1) which will work the same as chrome-wrapper.sh does.
  • write chrome-wrapper.py in Python and replace chrome-wrapper.sh with it. Then there is no need to support 2 different wrappers for different systems (I prefer this way, to be honest, but it will require more time).

bayandin avatar Jun 06 '17 10:06 bayandin

Will try to run it on Linux and understand how it works, then will try to create bat first. If I am not mistaken, by using chrome-wrapper as binary in ChromeOptions, we still should set the path to chrome driver binary as well?

SergeyPirogov avatar Jun 06 '17 10:06 SergeyPirogov

we still should set the path to chrome driver binary as well?

Did you mean Chrome (not chrome driver)? If so, then it's not required, In the wrapper, I've tried to mimic chromedriver's heuristic for finding Chrome's binary. But if you want to use custom binary (which is not in default locations), you can add an argument --chrome-binary to ChromeOptions' args.

bayandin avatar Jun 06 '17 11:06 bayandin

I meant chrome driver

SergeyPirogov avatar Jun 06 '17 11:06 SergeyPirogov

devtools-proxy doesn't require any changes of chromedriver usage (it requires only additional parameters in ChromeOptions). So if you set it without proxy, then you need to set it with the proxy.

bayandin avatar Jun 06 '17 14:06 bayandin