Securely back up files to encrypted hard drives and S3 buckets
Maintain multiple SSH and GPG keypairs across desktops, laptops, servers, and Github accounts
Securely back up emails and contacts so that they can be viewed offline
Laptop data encryption and hidden volumes
Setup servers with daemonized processes, monitoring, firewalls, email notifications, &c.
Maintain your dotfiles in source control to quickly deploy on new machines (like EC2 for remote pairing sessions)
One reason is the paradox of choice—we just have too many options!
Wikipedia lists 26 open source and 62 proprietary programs for backups alone. Can you tell which open source programs you’ll be able to get running on your machine in 2 minutes?
Another reason is that we can’t tell how long it’ll take.
You don’t want to figure this out yourself, because it’s a distraction from your core skills.
Since we don’t know what software works or how long it’ll take, we perpetually put off backing up our data and tidying up our servers until “next week”. And in the mean time, we just keep our fingers crossed that our disks don’t crash and our sites stay online.
Here’s a thought experiment to quantify your exposure: given 5 minutes notice, how much would someone need to offer before you’d sell your computer? E.g., if you have an 11" MacBook Air (MSRP $1200), would you demand $1500? $3000? $10,000?
Wouldn’t it be rad to not be tied to a specific piece of hardware? If there was no risk of losing a week (or more!) of billable hours or productive work recovering from a stolen laptop or crashed server. You’d be able to rest easy knowing that you have a tested, working process that YOU can use to manage your data and your systems.
DevOp targets the following platforms:
We test all scripts and tooling against these platforms, because these are what we use. If you use other platforms, we assume it’s because you know what you’re doing; most of our guides will probably work fine, but don’t ask us for help compiling programs on your screamin' DEC Alpha.
If you have any questions or concerns before buying, just send us an email.
The DevOp is 100% guaranteed. The refund policy is simple: if you buy the DevOp and feel like it was misrepresented, that it didn’t assuage your fears of data loss, or that it didn’t help you secure your Internet Cloud Dingus, then just send us an email asking for a refund. We’ll refund your money ASAP, no B.S.
“By the way, this stuff is awesome. I love it.” — Alexis Gallagher
“A great idea.” — Ryan Singer, 37signals
“I think it’s an amazing resource and I am sure that, as more content is added, I am going to keep on finding valuable insights (especially around using TrueCrypt, that was key for me).” — Bruno Mattarollo, Co-Founder and CTO at WaysAct
“More than worth the money.” — John P. Toohey
The DevOp is written by Kevin Lynagh; I’m a developer specializing in data visualization and Clojure. I’ve spoken at more than a dozen developer conferences around the world. I think open source is rad, and much of my work is on Github.
Writing good documentation and keeping up with the changing world of tech is a lot of work! Paying subscribers mean that we’ll always keep the guides up to date as new operating system and tooling versions are released. We dogfood all of this too, of course, so our interests are very aligned.
Yep; for the ramen startup or small agency with a benevolent “help our employees avoid bad computer mojo” policy, a shared DevOp plan can be purchased for $499/year for up to 20 employees. Please contact us if you want a larger plan.
We’re in this for the long haul, and are only interested in like-minded customers. In addition, having a subscriber base means that we’ll always have the resources to research, develop, and test new options.
That’s not a question! Please shoot an email to email@example.com and we’ll get you squared away.
Nope; all of the modules are written in plain ‘ol HTML. All software (both custom DevOp scripts and the exact, tested versions of open source libraries) are distributed as tarballs on a per-module basis.