Packaging Ruby and Rails Apps for Production
•
11 likes•9,522 views
This document discusses packaging Ruby and Rails applications for production. It covers using system packages versus gems, configuration management tools like Chef and Puppet, creating Debian packages, packaging gems, build servers, pain points like outdated Rubygems packages, and ideas for deeper Bundler integration and packaging gems by default. Overall it presents strategies for deploying Ruby applications as system packages for production servers.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Packaging Ruby and Rails Apps for Production
Similar to Packaging Ruby and Rails Apps for Production (20)
More from Fabio Kung
More from Fabio Kung (13)
Recently uploaded
Recently uploaded (20)
Packaging Ruby and Rails Apps for Production
- 1. packaging ruby and rails apps to production Fabio Kung Rodrigo Vaz
- 4. cap deploy
- 5. w"?
- 7. OMG... gem vs system pkgs again? disclaimer
- 8. it probably doesn’t apply to PaaS disclaimer
- 9. sysadmin love h+p://www.flickr.com/photos/theamarand/2879573829/
- 11. sysadmins and sysops know OS/distro tools http://www.flickr.com/photos/sequelguy/4390001903/
- 12. dpkg -l $ dpkg -l ii adduser 3.112ubuntu1 ii apt 0.7.25.3ubuntu9.3 ii apt-utils 0.7.25.3ubuntu9.3 ii aptitude 0.4.11.11-1ubuntu10 ii autoconf 2.65-3ubuntu1 ii automake 1:1.11.1-1 ii autotools-dev 20090611.1 ii base-files 5.0.0ubuntu20.10.04.2 ii base-passwd 3.5.22 ii bash 4.1-2ubuntu3 ii bash-completion 1:1.1-3ubuntu2 ii binutils 2.20.1-3ubuntu7 ii build-essential 11.4build1 ii bzip2 1.0.5-4ubuntu0.1 ii cdbs 0.4.62+nmu1ubuntu9 ii cmake 2.8.1-4~lucid1 ii cmake-data 2.8.1-4~lucid1 ii coreutils 7.4-2ubuntu2 ii cpp 4:4.4.3-1ubuntu1 ii cpp-4.4 4.4.3-4ubuntu5 ii cpu-checker 0.1-0ubuntu2 ii cron 3.0pl1-106ubuntu5 ii dash 0.5.5.1-3ubuntu2 ii debconf 1.5.28ubuntu4 ii debconf-i18n 1.5.28ubuntu4 ii debhelper 7.4.15ubuntu1 ii debianutils 3.2.2 ii debootstrap 1.0.28ubuntu1~lucid1 ii devscripts 2.10.61ubuntu5 ...
- 13. dpkg -L myapp dpkg --contents myapp.deb $ dpkg -L vim /. /usr /usr/bin /usr/bin/vim.basic /usr/share /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/vim /usr/share/bug /usr/share/bug/vim /usr/share/bug/vim/presubj /usr/share/doc /usr/share/doc/vim
- 14. dpkg -S /etc/myapp.conf $ dpkg -S /usr/bin/vim.basic vim: /usr/bin/vim.basic
- 15. apticron, cron-apt apticron report [Mon, 18 Apr 2011 18:25:02 -0300] ===================================================== apticron has detected that some packages need upgrading on: foo.locaweb.com.br [ 10.0.0.1 ] The following packages are currently pending an upgrade: myapp 5.1.0-3 myapp-assets 5.1.0-3 ====================================================== Package Details: Reading changelogs... --- Changes for myapp (myapp myapp-assets) --- myapp (5.1.0-3) stable; urgency=low * new awesome feature * lots of bug fixes -- Fabio Kung <fabio.kung@locaweb.com.br> Tue, 12 Apr 2011 22:31:11 -0300
- 18. db/seeds.rb
- 19. rake db:migrate rake assets:export rake i18n:js:export ...
- 20. package repositories distribute it
- 21. signed packages
- 22. dev toolchain in production servers?
- 23. build pipeline
- 24. tes;ng x stable
- 25. multiple archs
- 28. btw... rake db:migrate VERSION=old
- 29. dependencies
- 30. (re)deploying services must be ultra easy
- 31. package everything OH WAIT...
- 33. recipes cf-agent promisses cfengine, chef, rules cf-agent puppet cf-agent
- 34. package "sudo" do action :upgrade end user "sshservice" do system true action :create end template "/etc/sudoers" do source "sudoers.erb" mode 0440 owner "root" group "root" variables(:user => "sshservice") action :create end
- 35. bundle common control { bundlesequence => { "ssh" }; inputs => { "cfengine_stdlib.cf" } } bundle agent ssh { packages: "sudo" package_policy => "add" package_method => "deb" files: "/etc/sudoers" edit_defaults => empty, edit_line => expand_template("sudoers.in"), perms => mog("0440", root, root), create => "true"; methods: "sshservice" usebundle => create_user("sshservice") }
- 36. rule of thumb
- 37. keys ssh, access, crypt, passwords, ...
- 39. configuration files <any>.yml.example
- 40. database.yml.example CFEngine3 production: adapter: mysql2 encoding: utf8 database: ${db_name} username: ${db_user} password: ${db_password} host: ${db_address} edit_line => expand_template("database.yml.example")
- 41. database.yml.example Chef, Puppet production: adapter: mysql2 encoding: utf8 database: <%= db_name %> username: <%= db_user %> password: <%= db_password %> host: <%= db_address %>
- 43. creating packages http://www.flickr.com/photos/miadcommunicationdesign/3169997945/
- 44. debian/control Source: myapp Section: web Priority: extra Maintainer: Fabio Kung <fabio.kung@locaweb.com.br> Build-Depends: debhelper (>= 7) Standards-Version: 3.8.3 Homepage: https://github.com/locaweb/myapp Package: myapp Architecture: any Depends: rubygems (>= 1.3.6), libapache2-mod-passenger (>= 2.2) Description: my great new app Visit https://mycompany.com/myapp for more information
- 45. debian/changelog myapp (0.0.2) unstable; urgency=low * Applying SOLID after attending railsconf 2011 * using Devise -- Fabio Kung <fabiokung@locaweb.com.br> Wed, 18 May 2011 08:00:30 -0300 myapp (0.0.1) unstable; urgency=low * Initial release -- Rodrigo Vaz <rodvaz@locaweb.com.br> Wed, 17 May 2011 18:05:20 -0300
- 46. debian/rules
- 48. • dpkg-buildpackage • pbuilder • cowbuilder
- 49. why is it unusual?
- 50. debian-ruby- maintainers Giving up on Ruby packaging - Lucas Nussbaum http://www.lucas-nussbaum.net/blog/?p=617
- 51. FPM awesome https://github.com/jordansissel/fpm I want a simple way to create packages without all the bullshit. In my own infrastructure, I have no interest in Debian policy and RedHat packaging guidelines ‐ I have interest in my group's own style culture and have a very strong interest in ge6ng work done. ‐‐ Jordan Sissel
- 54. http://morethanseven.net/2011/01/16/Why-developers-should- care-about-system-packages.html Why Developers Should Care About System Packages -- Gareth Rushgrove
- 55. what about other platforms?
- 56. blaming game what are we doing to end it?
- 58. a long way to go...
- 59. RPM
- 60. bundle debianize (?) bundler deeper integration, plugin
- 62. vendor everything vs package everything gem dependencies
- 63. packaging gems • fpm • gem2deb • gem2rpm • checkinstall • debian/ changelog from git log
- 64. build servers
- 66. REST API POST /project: name="myapp" version="1.0.1" git_url="git://host/project/repository.git" branch="master" build_cmd="rake prepare" install_cmd="rake install PREFIX=debian/tmp" respository_url="ftp.location.com" repository_user="a_user" repository_passwd="a_g00dP455w0rd"
- 68. pain points • old rubygems official system packages • bundler (!) • package yourself • PPA?
- 69. Thanks! fabio.kung at gmail, @fabiokung rodrigo.vaz at gmail, @rodrigovaz additional info: https://wiki.ubuntu.com/PackagingGuide http://morethanseven.net/2011/01/16/Why-developers-should-care-about-system-packages.html https://github.com/jordansissel/fpm http://www.lucas-nussbaum.net/blog/?p=617
Editor's Notes
- \n
- infrastructure coding\n
- \n
- \n
- \n
- \n
- NO! and yes. :-)\n**my** packages on **my** servers\nprivate repositories\n
- \n
- \n
- multiple systems\nmultiple languages\nmultiple architectures\nsystem packages provide a lot of useful features\n
- what is installed?\nwhat are the versions?\nwhat is the _current_ version of my app?\n
- what are the config files?\nwhat is included?\n
- what is the package of this file?\n
- \n
- \n
- learning from operating systems, self-test boot\ndiff .example .conf\nexternal systems, api versions, required assets, filesystem, required users, fixtures, ...\nit&#x2019;s all about dependencies! (other than package dependencies)\n
- \n
- bytecode precompilation\n
- package => many projects\nsame package => many machines\nmultiple versions\n
- \n
- avoid compilation/build on production servers \ngcc, make, g++, libc-dev, etc\nrvm, git, ... the more crap you have in prod servers => the more to exploit\n\n
- **same package** being deployed at different staging environments\n
- \n
- \n
- \n
- \n
- pre/postrm\n
- \n
- rebuildable servers\nservers/machines as code\nrecreating machines => easy\n
- what goes inside the package? what doesn&#x2019;t?\n
- \n
- Configuration Managers\n
- chef receipt\n
- cf promisse\n
- it belongs to your app => put it inside the package\nunless you expect it to be changed\nare people going to edit it after installing the package?\n
- \n
- deb, rpm offer easy ways to create them\n
- as we are all doing\n
- \n
- \n
- assets server\n
- dh_make\ndebian/{control,rules,changelog}\ndpkg-buildpackage -> rules, sign\ndebian maintainers policy, ubuntu packaging guide\n
- \n
- \n
- \n
- \n
- \n
- why things seem to be slower in the ruby vs system packages camp?\nwhy just a few people seems to be caring?\n
- \n
- \n
- \n
- rubygems, ruby and passenger debs\n
- \n
- tools\nnot usual to &#x201C;build&#x201D; stuff on production servers\nplatforms offer easy ways to make binary/system packages\nruby is probably missing that. Nobody is caring\n
- \n
- \n
- \n
- \n
- other ideas:\n - rvm gemset package\n - rvm rubies package\n
- \n
- \n
- \n
- cloud IaaS and VMs help a lot\nbricklayer\nlaunchpad\nCI servers (hudson, bamboo, teamcity, ...)\n\n
- - Watch git repositories\n- Build snapshots for each commit\n- Watch for tags testing_1.2.3 and stable_1.2.3\n- Promote packages to a ftp server (which runs reprepro or any other debian repository tool)\n- Has a rest API\n- Has cocoa-like web interface wrote with cappuccino framework\n- Batteries are included except redis server\n\n\n
- \n
- - Lauchpad generate binaries out of your source as long as your application is already ready to be packaged\n- Build packages for multiple archs\n- Host the package in a repository called PPA\n- Developed and open source by canonical\n
- \n
- \n