Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Voxera648216dI have not used proxy since 1997 so no its not been a problem during the last 20+ years of development.
netikras1143816dNo that won't be fixed by wsl. And no, linux won't make it any easier.
How about scripting your configuration changes? And wrapping your apps' launchers to scripts so they would pick up proxies as they are launched?
P.S. Hiding everything behind proxies is a silly solution. Tho I wonder why did your company chose that path...
noder120316d@netikras Thanks. Scripting all startup scripts is what I am trying in my machine these days. Works with some of them, not for others, especially IDEs.
Bigger problem is, when other devs in my team come to me with their build issues, npm/maven dependencies not getting downloaded, external API calls failing from their code etc.. Like, why their auth server is returning HTTP 401 even with a valid token, whereas the actual problem is the validation API could not even connect to the auth server, hence throws the 401. So, I have to go into their machine, check all levels of proxies and find out which one of them incorrect :(
netikras1143816d@noder hey here's a crazy idea.. How about setting up a custom gateway [linux pc?] that would act as a proxy btwn your computers and the actual gw [but you'd use it as a gw, not as a proxy; an infra abstraction layer]? This way you'd only have to do proxy configurations on that gw rather than on every app in every dev's pc, every day.
jimbobbles9415dStart recording the amount of time you and everyone else spend dealing with proxy issues. After a month add up the time, and multiply it by a reasonable salary. Then send that to your manager and ask them if they want to increase the companies profits by that much, every month. Then tell them how (@netikras seems to have a really nice solution)
LynxMagnus178615dWe had that problem, you'll have the same issues on WSL and Linux.
Problem is with your network restrictions. We gave all our developers "off network" development machines to alleviate the problem.
ddephor417415d@netikras It's the easiest way to create a bottleneck to plug all those tools to.
Thing is, the non-tech people just don't care, they only create traffic over standard ports with a few tools the IT dept knows about. But devs have to use stuff, IT dept can never think of. So sometimes it's a fight to get everything working.
I still have two issues driving me crazy every other day, but they will not be solved, because IT dept argues about "security issues" and then no manager will decide against that decision. So I have to work my way around, it takes much more time, but I told 'em what I would need and as long as I get paid for that extra time, it's kind of OK for me.
notcool215415dI feel you man proxy sucks in Linux too. You need to configure most of them individually. Fuck proxy. Just Fuck.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job