Until Dockrap (and its various predecessors and friends) are compatible with IT depts setting their VPN config to disallow local network access, fuck all that hipster stuff and use good old self-configured services. Hipster bullshit that can't be used in any org that remotely takes care of their network (hint: any big corporation will mandate this by contracts with huge liability figures in the contracts).
To the users: if you can't configure a simple local web server for development, you should not be qualified to develop a web service. Period. (Hint: Apache and PHP is included in OS X, but a bit outdated to be fair - but you can install/upgrade to a OAMP stack using MacPorts in MINUTES)
I know how macports works. I just don't want my whole team to deal with small differences which cause the dreaded "works on my machine". I'm not saying docker is perfect, but at least those guys[Docker inc.] are trying to make a shift to something at least a bit more immutable then what you are suggesting.
Bigco needs to get with it or get out of the way. Whenever a bloated, antiquated dinosaur is replaced by a newer, smarter company the sun shines a little brighter in my world.
> Whenever a bloated, antiquated dinosaur is replaced by a newer, smarter company the sun shines a little brighter in my world.
And whenever a "newer, smarter company" disregards fundamental IT security practices and gets hacked, the sun shines a little brighter in my world.
Security is an afterthought (if a thought at all) in many hipster operations, and it's about time someone fucks up so badly that IT security is priority #1 from the beginning.
To the users: if you can't configure a simple local web server for development, you should not be qualified to develop a web service. Period. (Hint: Apache and PHP is included in OS X, but a bit outdated to be fair - but you can install/upgrade to a OAMP stack using MacPorts in MINUTES)