289 karma · joined December 23, 2013
Otherwise, on our fleet of hundreds of IIS, we've had success just pointing IIS to a hardlink, deploying the new version to a new folder and updating the hardlink - from memory this does trigger an app pool restart but its super fast, lets you go back and forth very easily.
Now, sure, technically there may be circumstances when you can technically/legally shift liability. But your customers don't care - they have the relationship with you. So the third parties problems, are your problems.
Everyone gets here eventually and you can just fight over stuff like “is an alb shared regional or app specific”
In the words of Raymond Chen this exploit is basically being on the other side of the air tight hatch
Honestly, learning to read code and execute it in your head is a super power
For me, Github/personal projects have not been a useful signal either way, but it is apparent in recentish years that the advice has been to have one regardless.
Thus it requires a "replicaset" but it's fine to run a single node replicaset.
Everyone seems to want to worry about “nation state actors” and getting with novel 0 days when in fact missing the basic low hanging fruit is likely to result in far more damage