This document discusses best practices for deploying software projects. It outlines five rules: 1) implement deployment from the beginning, 2) automate everything, 3) test quality, 4) create deployable artifacts, and 5) run deployments with one invocation. Specific recommendations include using Puppet for configuration, building testable artifacts, choosing a deployment tool like Fabric or Capistrano, and automating the entire deployment process.

2. The Last Mile
Problem

6. Development Live

7. The Dog
Ate My Deployment

8. Rule 1:
Implement deployment at the
beginning of your project

9. +
https://puphpet.com/

10. Every configuration has to be
done by Puppet

11. Developers and Operations
share the same configuration

12. Rule 2:
Automate everything

15. Create Targets
For Everything

16. Structure Your
Ant Files

17. Use A Framework For This
http://abc.tools.qafoo.com/

18. $ ant build

19. Rule 3:
Test the quality of your
project

21. Jenkins PHP Template
http://jenkins-php.org/

22. PHP QA Tools

23. Too many violations should
break your builds

24. Test performance factors
of your application

25. $this->assertLessThan(
10,
$profile->getCollector('db')
->getQueryCount()
);

26. Rule 4:
Create deployable artifacts

27. Build them so that they only
need configuration to run

28. Create them once reuse
them in all deployments

29. Continous
Integration
Testing Staging Live

30. Rule 5:
Run your deployment with
only one invocation

32. Choose Your
Deployment Tool

33. Choose It
With Your Operations Team

34. Shell Scripts

36. Choose A Tool
That Helps You

37. Fabric

38. Capistrano

39. Rex

40. group myserver => "server-a", "server-b";
task "deploy", group => "frontend", sub {
deploy $tarball;
needs "configure";
needs "test";
};

41. Keep Your Deployment
Configuration With Your Code

42. $ rex deploy –-tarball=version1.0.1.tar.gz