A life of a developer behind a company firewall is tough. Add additional complications for a windows developer.
Saying that a development process of an Edge tech stack is pretty uniform across three major platforms (Windows, MacOS, Linux) and is reasonably transparent with right settings.
Here is a collection proxy-related setting for different components and tools you will be using across Proxy SDLC in a single place.
curl | cli: curl -x http://127.0.0.1:8080 <url> ~/.curlrc proxy = <proxy_host>:<proxy_port> |
git | git config http.proxy http://host:port |
vscode | Preferences/User Settings { "http.proxy": "http://my.proxy.address:8080", "https.proxy": "http://my.proxy.address:8080", "http.proxyStrictSSL": false } |
java/maven plugin | Linux: export MAVEN_OPTS="-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8080 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=8080" Windows: set MAVEN_OPTS=-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8080 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=8080 |
npm | npm config set proxy http://proxy.company.com:8080 npm config set https-proxy http://proxy.company.com:8080 |
maven | {M2_HOME}/conf/settings.xml <proxies> <proxy> <id>optional</id> <active>true</active> <protocol>http</protocol> <username>mkyong</username> <password>password</password> <host>proxy.mkyong.com</host> <port>8888</port> <nonProxyHosts>local.net|some.host.com</nonProxyHosts> </proxy> </proxies> |
request/node.js | var r = request.defaults({'proxy':'http://localproxy.com'}) |