Rails Deployment Audit (July 13, 2012)
Vim (June 27, 2012) - Part I
Vim Tips - Part II (July 3, 2012)
Rails 3 upgrade process (the road from 2.3.14 to 3.2.6) (June 21, 2012)
Intro to (December 30, 2011) in Ruby
Remote pair-programming with Screen (November 3, 2011)
Redis in the (December 28, 2011) ecosystem
…preparation, it can be a seamless transition. As a member of the Professional Services and Deployment teams, I've handled many migrations to Engine Yard as well as between Engine Yard environments and wanted to share some best practices.
Before you plan the migration, it is very important to test out the application on the new environment. Some of the more painful migrations I have been involved with were a result of incomplete testing. Functionality should be tested but it is …
Like Continuous Deployment, whereby IMVU deployed changes to their web application +50 times per day, BetaBrand's aim is to put out a new product every day. They manufacture only a small batch of a particular product, but enough to come to a decision point:
"If there's anything that we've learned from our customers, it's that with the first hundred to two hundred pair sold, we can make minor changes on it to improve it and retest, we can turn it into an entire line, …
The multiple monitors . I'm amused.has discovered
DynamoDB for the Uninitiated - A simple spike in Ruby.
Continuous Deployment with - Pretty easy to wire up as it turns out. and Jenkins
Ruby - Shots promo for a new ebook that is putting together.
Love story If you're runningon …
CLI Deployment System Deployment history is only available on the web using the CLI-based deployment method. If you haven't already converted your environment to CLI Deploys, now is the time.
Switching your environments to use the CLI deploy system as the strategy for web deployments only takes a few seconds. There have been no reported issues for this well tested deploy system, and about half of all Engine Yard AppCloud environments are using it.
Benefits of CLI Deploy
…Railsconf was in June of 2006 and we had a teaser website up and I was giving a talk on Rails Deployment at the conference. I announced the then vaporware Engine Yard as my "One more thing" at the end of my speech and linked to our site where we took emails.
We rounded up about $120k by begging, borrowing and stealing(not really) from friends and family. I must admit that Tom and Lance raised most of this first money here while I was busy writing the first code for Engine Yard…
Continuous Deployment,and Pre-Tested Commits on Digg4 | Digg About - talks about how they're doing continuous deployment and mention tools too.
Pricing - Harmony Website Management - is finally being opened up to the public. They've announced pricing.
Chromium Updater | Sean's Bloggity - My last updater clobbered itself and chromium, so I killed it and was using the updater plugin, but that's a manual process. So …
Designing and Deployment of a fully virtualized enterprise.
1. Replacement of all desktops with thin clients.
2. Move from hosted email to a virtulized exchange environment.
3. iscsi based storage for everthing.
4. Blade Based Servers
1. When your designing your blades, use at least a single SSD
drive to host ESX hypervisor. Yes, you can boot iScsi, yes you can
use a SD card.
Of all the Lean Startup techniques, Continuous Deployment is by far the most controversial. Continuous Deployment is a process by which software is released several times throughout the day - in minutes versus days, weeks, or months. Continuous Flow Manufacturing is a Lean technique that boosts productivity by rearranging manufacturing processes so products are built end-to-end, one at a time (using singe-piece flow), versus the more prevalent batch and queue approach.