The document discusses the deployment process, emphasizing essential steps such as optimizing assets, running database migrations, and providing rollback functionality. It introduces tools like Grunt for asset optimization and Capistrano for server automation and deployment, outlining its configuration and usage for various programming languages. The document also suggests further resources for infrastructure management and continuous integration for automated deployments.

1. Deploy like a Pro
Damián Serrano Thode
@dsthode
MalagaMakers GeekBeers (20150115)

2. What is deployment?

3. Copy source files to the server
What is deployment?

5. Copy source files to the server
Not just that!
What is deployment?

6. ✔
Optimize assets
What is deployment?

7. ✔
Optimize assets
✔
Run database migrations
What is deployment?

8. ✔
Optimize assets
✔
Run database migrations
✔
Restart dependent services
What is deployment?

9. ✔
Optimize assets
✔
Run database migrations
✔
Restart dependent services
Provide rollback functionality
What is deployment?

11. Optimize assets

12. Optimize assets
Enter Grunt → http://gruntjs.com

13. Optimize assets
Combine and minify javascript

14. Optimize assets
Combine and minify javascript
You can use grunt-contrib-uglify

15. Optimize assets
Preprocess, combine and minify styles

16. Optimize assets
Preprocess, combine and minify styles
You can use grunt-contrib-sass &
grunt-contrib-cssmin

17. Optimize assets
Optimize and combine images

18. Optimize assets
Optimize and combine images
You can use grunt-spritesmith &
grunt-contrib-imagemin

19. Optimize assets
Optimize and combine font files
(SVG only)

20. Optimize assets
Optimize and combine font files (SVG only)
You can use the same grunt-contrib-imagemin

21. Database
migrations,
deployment &
rollback

22. Enter Capistrano → http://capistranorb.com

23. “A remote server automation and
deployment tool written in Ruby.”
“Capistrano is written in Ruby, but it can
easily be used to deploy any language.”

24. Run “cap install” on your project folder

25. Capfile defines requirements for your deployment tasks→
config/deploy.rb shared configuration for all the stages→
config/deploy/*.rb defines multiple stage deployment→
lib/capistrano/tasks where your custom tasks are defined→

26. Lots of tasks off-the-shelf that integrate with the Ruby on
Rails framework
bundler, assets, migrations, Passenger, etc...
You just need to include the gems in your Gemfile and
uncomment the require in the Capfile

27. Sample Capfile

28. Sample config/deploy.rb

29. Sample config/deploy/production.rb

30. Different roles available:
app, web, db
Also, you can define several servers at once, eg:

31. Available tasks

32. Deployment
Run 'cap <stage> deploy' on your console

33. Deployment flow

34. Rollback
Run 'cap <stage> deploy:rollback' on your console

35. Rollback flow

36. You can attach to any step to run custom commands using
'before' and 'after' from Capistrano DSL, eg:

37. Not a Rails shop?
You might need manual work creating your recipes,
although there is some hope in certain cases:
capistrano-node-deploy Node.js apps→
capistrano-virtualenv virtualenv python apps→
capistrano-django Django apps→
capistrano-go Go apps→
Caveat emptor! Might be old, untested or unsuitable

38. Where to go from here?
Infrastructure management tools like Chef or Puppet for
server provisioning
Continuous integration hooks for automated deployment to
staging servers

39. Talk deployed
Questions?
Damián Serrano Thode
@dsthode
MalagaMakers GeekBeers (20150115)