I’ve been thinking way too much about the SyFy series “Blood Drive.”
Over the last few weeks, as mentioned before, my colleagues and I have been working to implement a proxy server solution. One of the more aggressive bugbears we’ve fought is the size and complexity of our network — we have dozens of different network segments, some of which have pre-existing proxies, many of which are out of my team’s control. Finding a solution that worked well, everywhere, was tricky. But we’ve made progress.
At work, I’ve spent much of the last several weeks working on deploying a proxy service. A proxy is a service that can retrieve and cache Web pages on behalf of a large number of users.
In theory, you can use it to save bandwidth and protect your users by stopping viruses and such before they reach the users’ desktops. In practice, it’s mostly used to make sure your employees aren’t screwing around on Facebook at work.
No, not that Enterprise.
Nope. Try again.
This is about “the enterprise,” the notion of organizations that upgrade software less often than once every six weeks, and one vendor that wants to push things along, no matter the cost to the users…
I had a software installer that needs to be distributed with its license key, but in a way that keeps the users safe from themselves, and us safe from auditors. Find out how I did this in about an hour with NSIS below…
Here’s a link to my slides for the #wcstl presentation “Making Simple Things Really Complicated: High Availability for WordPress”. Enjoy!
Someday soon, I’ll try to pull out the most important notes from the slides and put them here, to make the search engines happy. (Or can Google and friends handle PDFs these days? I really don’t know.)