4. "In my business, I have some criteria that we follow for migrating websites live based on the needs of clients. Often I’m replacing an existing site, which means I do things such as backup the old site, begin migration, create any 301 redirects needed to maintain traffic," and do a final test of all pages, links, forms and functionality on the site."
6. Rackspace Tools like Capistrano, Fabric, Chef and Puppet allow you to build both simple and complex automation around your servers and application deployments. They broke the deployment process into three main areas.
7. Cont. The first step for a deployment process should be planning out the tasks. Any new code deployed should first be tested in a staging environment that closely matches production.
9. The basic workflow goes like this: • Push changes to a branch • Wait for the build to pass on our CI server • Tell Hubot to deploy it • Verify that the changes work and fix any problems that come up • Merge the branch into master
10. Not too long ago, however, this system wasn't very smart. A branch could accidentally be deployed before the build finished, or even if the build failed. Employees could mistakenly deploy over each other. As the company has grown, we've needed to add some checks and balances to help us prevent these kinds of mistakes.
11. Now they.. The first thing we do now, when someone tries to deploy, is make a call to Janky to determine whether the current CI build is green. If it hasn't finished yet or has failed, we'll tell the deployer to fix the situation and try again.
12. That's All Folks Thank you Orange Blossom Media for your support !
13. Credits • Orange Blossom Media: Information was provided by David L. • Rackspace: Information was found on Rackspace Blog • Github: Information was found on Rackspace Blog • Presented by Free Rosas
