This recipe lets you run Docker within Docker.
This post demonstrates some powerful dtrace scripts for OS X.
Did you know that OS X has dtrace running on it?! I didn’t.
I want a Vagrant box on which to configure and develop WordPress. Here are some of the options. I wanted to decide on one. Here is how.
- Box: name
- Stars: on GitHub, # stars
- Ctrb: on GitHub, # contributors
- Rel: on GitHub, # releases
- Cmts: on GitHub, # commits
- Brn: on GitHub, # branches
- For: Purpose of box
- Rct: Gut reaction 1
*: Pros and Cons
- Rt2: Gut reaction 2
- Identify options
- Classify them by stars and contributors
- Get a gut reaction whether to dig deeper or not
- Review them again
VVV seems to be the best place to start.
When you create VMWare Fusion virtual machines through the GUI they are stored in
When Vagrant creates VMWare Fusion virtual machines they are stored in
Confirmed it myself.
Thank you JT Gray.
When you purchase the VMWare provider for Vagrant on Windows you learn that the provider name is
vmware_desktop. The only time that you will ever use this name is when you install the provider and the license. If you use that provider name anywhere else you will get message
The provider ‘vmware_desktop’ could not be found, but was requested to back the machine ‘default’. Please use a provider that exists.
The correct provider name is
You might mix up the two names when specify a provider when you are bringing a box up. I did it. He did it. It is easy to do, especially if you scan a box page to find the provider name. The name there is for the name to install the license, not to start up a box.
This “issue” has been around for over a year and wastes about an hour of your time if you are facing it on Windows.
Windows Azure: The Big Picture.
You won’t view anything in this video and say “Oh my goodness I never imagined you could do that with a computer”. What will happen though is that now you will know how Azure lets you do that with a computer, all of their offerings from virtualization to networking to message queues covered. That is great to know. I chose this video specifically because it is the shortest. Further digging is required.
The Case for PowerShell.
Brief, terse, compact, too many jokes. Excellent details. Not training, rather informational. Must have scripting/automation experience to appreciate the implications of what is covered. Without that experience, the presentation could be viewed as too light-weight.
IIS for Developers.
Brief, terse, compact. Excellent details required to deploy a system to IIS. Not training, rather informational. Must have server/system-deploy experience, and therefore questions, before viewing.
Introducing DevOps to your organization can be done really, really simply.
First have the project team lead set up the development environment on his machine, all the while documenting how to do so. Second have a another team member follow and execute the steps. The lead and team member should discuss and review the process and make improvement. Third, have an engineer totally unfamiliar with the project follow the steps to the point where he can successfully run the automated tests in less than sixty minutes.
When this may be done successfully, it is time for a DevOps engineer to automate that process.
Here is a hyper-v plugin for Packer.io.
Great to see the infrastructure taking off for Windows.