Download as PDF, PPTX
![Deployment Examples ! ! Define hosts in inventory file [webservers] foo.example.com bar.example.com
www[01:50].example.com ! [dbservers] one.example.com two.example.com three.example.com](https://image.slidesharecdn.com/symfonylivenyc2014-rocksoliddeployment-141009101853-conversion-gate02/75/Symfony-Live-NYC-2014-Rock-Solid-Deployment-of-Symfony-Apps-119-2048.jpg)
![App Metrics: liuggio/statsd-php-client Deployment Complement Tools $sender = new SocketSender(/*'localhost', 8126, 'udp'*/); ! $client = new StatsdClient($sender); $factory = new StatsdDataFactory('LiuggioStatsdClientEntityStatsdData'); ! // create the data with the factory $data[] = $factory->timing('usageTime', 100); $data[] = $factory->increment('visitor'); $data[] = $factory->decrement('click'); $data[] = $factory->gauge('gaugor', 333); $data[] = $factory->set('uniques', 765); ! // send the data as array or directly as object $client->send($data);](https://image.slidesharecdn.com/symfonylivenyc2014-rocksoliddeployment-141009101853-conversion-gate02/75/Symfony-Live-NYC-2014-Rock-Solid-Deployment-of-Symfony-Apps-129-2048.jpg)
![App Metrics: liuggio/statsd-php-client Deployment Complement Tools $data[] = $factory->timing('usageTime', 100);! ! // send the data as array or directly as object $client->send($data);](https://image.slidesharecdn.com/symfonylivenyc2014-rocksoliddeployment-141009101853-conversion-gate02/75/Symfony-Live-NYC-2014-Rock-Solid-Deployment-of-Symfony-Apps-130-2048.jpg)
![App Metrics: liuggio/statsd-php-client Deployment Complement Tools $data[] = $factory->increment('orders');! ! // send the data as array or directly as object $client->send($data);](https://image.slidesharecdn.com/symfonylivenyc2014-rocksoliddeployment-141009101853-conversion-gate02/75/Symfony-Live-NYC-2014-Rock-Solid-Deployment-of-Symfony-Apps-131-2048.jpg)
![App Metrics: liuggio/statsd-php-client Deployment Complement Tools $data[] = $factory->gauge('memory', 333);! ! // send the data as array or directly as object $client->send($data);](https://image.slidesharecdn.com/symfonylivenyc2014-rocksoliddeployment-141009101853-conversion-gate02/75/Symfony-Live-NYC-2014-Rock-Solid-Deployment-of-Symfony-Apps-132-2048.jpg)
Uploaded byPablo Godel
Symfony Live NYC 2014 - Rock Solid Deployment of Symfony Apps
The document provides an extensive overview of deploying Symfony applications, emphasizing the importance of reliable and automated deployment processes. It discusses various deployment methodologies, challenges, and best practices such as ensuring development environments closely resemble production, using tools for automation and monitoring, and addressing common pitfalls. Additionally, it mentions tools like Ansible, Capistrano, and logging solutions for effective deployment management.
Symfony Live NYC 2014 - Rock Solid Deployment of Symfony Apps
- 1. Pablo Godel ! @pgodel! https://joind.in/12199 RockSolid Deployment of Symfony Applications Photo:AlvaroVidela
- 2. Hi, I amPablo.
- 3. Hi, I amPablo. ! @pgodel
- 5.
- 6. Deployment Software deployment isall of the activities that ! make a software system available for use. http://en.wikipedia.org/wiki/Software_deployment
- 7. Deployment A very importantpart of the application life-cycle
- 8. Deployment A very importantcritical part of the application life-cycle
- 9. Deployment It should notbe an ! after thought
- 10. Deployment It should bepredictable
- 11. Deployment The more youdo it the better it goes
- 16.
- 17. 1. Open anaccount
- 18.
- 19.
- 20.
- 22.
- 23.
- 24. $ git pushheroku master!
- 26. $ heroku ps:scaleweb=5!
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52. Deployment starts withthe developer Deployment Fact #1
- 53. Deployment starts withthe developer • Development environment must be as close as possible to productions servers! Deployment Fact #1
- 54. Deployment starts withthe developer • Development environment must be as close as possible to productions servers! • Setup test/qa/staging servers! Deployment Fact #1
- 55. Deployment starts withthe developer • Development environment must be as close as possible to productions servers! • Setup test/qa/staging servers! • Use Vagrant to manage VMs! Deployment Fact #1
- 56. Deployment starts withthe developer • Development environment must be as close as possible to productions servers! • Setup test/qa/staging servers! • Use Vagrant to manage VMs! • Use Containers with Docker! Deployment Fact #1
- 57. Deployment starts withthe developer • Development environment must be as close as possible to productions servers! • Setup test/qa/staging servers! • Use Vagrant to manage VMs! • Use Containers with Docker! • Automate your development environment setup (Ansible, Homebrew Cask) Deployment Fact #1
- 58. Success depends onserver OS setup Deployment Fact #2
- 59. Success depends onserver OS setup • Automate installation/configuration with Ansible/ Puppet/Chef ! Deployment Fact #2
- 60. • Automate installation/configurationwith Ansible/ Puppet/Chef ! • Create OS packages for 3rd party software Deployment Fact #2 Success depends on server OS setup
- 61. • Automate installation/configurationwith Ansible/ Puppet/Chef ! • Create OS packages for 3rd party software! • Setup your own package (rpm/deb) repositories Deployment Fact #2 Success depends on server OS setup
- 62.
- 63. Monitoring is uptime •Use tools to know what is going on with your servers (Ganglia, Cacti, Zabbix, etc.)! Deployment Fact #3
- 64. Monitoring is uptime •Use tools to know what is going on with your servers (Ganglia, Cacti, Zabbix, etc.)! Deployment Fact #3
- 65. Monitoring is uptime •Use tools to know what is going on with your servers (Ganglia, Cacti, Zabbix, etc.)! • Add metrics to your app (Graphite, StatsD, New Relic)! Deployment Fact #3
- 66. Monitoring is uptime •Use tools to know what is going on with your servers (Ganglia, Cacti, Zabbix, etc.)! • Add metrics to your app (Graphite, StatsD, New Relic)! • Use your logs wisely (Logstash, Hecka, Kibana) Deployment Fact #3
- 67.
- 68.
- 69. Deployment Methodologies • VIM-style! •FTP uploads
- 70. Deployment Methodologies • VIM-style! •FTP uploads
- 71. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync
- 72. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync! • Source control (GIT, SVN)
- 73. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync! • Source control (GIT, SVN)! • Build tools (Ant, Phing, Jenkins)!
- 74. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync! • Source control (GIT, SVN)! • Build tools (Ant, Phing, Jenkins)! • Package based (RPM, DEB, …) !
- 75. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync! • Source control (GIT, SVN)! • Build tools (Ant, Phing, Jenkins)! • Package based (RPM, DEB, …) ! • Specialized tools (Capifony, Deployer, …)!
- 76. Deployment Methodologies • VIM-style! •FTP uploads! • Rsync! • Source control (GIT, SVN)! • Build tools (Ant, Phing, Jenkins)! • Package based (RPM, DEB, …) ! • Specialized tools (Capifony, Deployer, …)! • IT automation tools (Ansible, Puppet, Chef, …)
- 77.
- 78. Deployment: First time •Copy files to server(s)! • Set server-side configurations! • Load DB fixtures! • Process and install assets! • Warm up cache! • Enable site
- 79. Deployment: Subsequent times •Copy files to server(s)! • Update server-side configurations! • Update DB (migrations)! • Process and install assets! • Warm up cache! • Enable new version
- 80.
- 81.
- 82.
- 83. • use sshbased connections! Challenge: Secure Deployment Challenges
- 84. • use sshbased connections! • don’t store passwords on source control Challenge: Secure Deployment Challenges
- 85. • use sshbased connections! • don’t store passwords on source control! • use environment variables for sensitive data Challenge: Secure Deployment Challenges
- 86. Challenge: Static assets DeploymentChallenges
- 87. Challenge: Static assets •Minimize/combine JS and CSS files! Deployment Challenges
- 88. Challenge: Static assets •Minimize/combine JS and CSS files! • Enable web server compression! Deployment Challenges
- 89. Challenge: Static assets •Minimize/combine JS and CSS files! • Enable web server compression! • Add versioning to static assets links (code.js?v=1)! Deployment Challenges
- 90. Challenge: Static assets •Minimize/combine JS and CSS files! • Enable web server compression! • Add versioning to static assets links (code.js?v=1)! • Run utilities locally or in a staging server, create artifact, deploy result! Deployment Challenges
- 91. Challenge: Static assets •Minimize/combine JS and CSS files! • Enable web server compression! • Add versioning to static assets links (code.js?v=1)! • Run utilities locally or in a staging server, create artifact, deploy result! • Serve static files from subdomain / CDN Deployment Challenges
- 92. Challenge: File permissionconflicts Deployment Challenges
- 93. Challenge: File permissionconflicts • Run Apache/PHP with same user! Deployment Challenges
- 94. Challenge: File permissionconflicts • Run Apache/PHP with same user! • Use php-fpm instead of mod_php! Deployment Challenges
- 95. Challenge: File permissionconflicts • Run Apache/PHP with same user! • Use php-fpm instead of mod_php! • Create “deploy” user and add web server to the group Deployment Challenges
- 96. Challenge: File permissionconflicts • Run Apache/PHP with same user! • Use php-fpm instead of mod_php! • Create “deploy” user and add web server to the group! • Use setfacl to give write access to multiple users! Deployment Challenges
- 97. Challenge: File permissionconflicts • Run Apache/PHP with same user! • Use php-fpm instead of mod_php! • Create “deploy” user and add web server to the group! • Use setfacl to give write access to multiple users! • Use external services for writing files and create readonly installations Deployment Challenges
- 98.
- 99. • Case sensitivefilesystems! Common Pitfalls
- 100. • Case sensitivefilesystems! ! src/Acme/ClassName ! != ! src/Acme/Classname.php Common Pitfalls
- 101. • Case sensitivefilesystems! ! src/Acme/ClassName ! != ! src/Acme/Classname.php Common Pitfalls
- 102. • Case sensitivefilesystems! • Configuration differences! Common Pitfalls
- 103. • Case sensitivefilesystems! • Configuration differences! • Outdated 3rd party software Common Pitfalls
- 104. • Case sensitivefilesystems! • Configuration differences! • Outdated 3rd party software! • Github down Common Pitfalls
- 105. • Case sensitivefilesystems! • Configuration differences! • Outdated 3rd party software! • Github down $ git daemon --base-path=/git/repo/path/ -- export-all! ! $ git clone git://127.0.0.1/repo! http://ozmm.org/posts/when_github_goes_down.html Common Pitfalls
- 106. • Case sensitivefilesystems! • Configuration differences! • Outdated 3rd party software! • Github down Common Pitfalls
- 107.
- 108. Simplest continuous deploymentever! <?php ! ! exec(‘/usr/bin/env -i HOME=/var/www git pull’);! echo “All done!”; hook.php Deployment Examples
- 109. <?php ! ! exec(‘/usr/bin/env -iHOME=/var/www git pull’);! echo “All done!”; hook.php screenshot Deployment Examples GitHub hook Simplest continuous deployment ever!
- 110.
- 111. Capistrano / Capifony •Ruby based! • Very extensible! • Large number of extensions! • Simple client side installation Deployment Examples
- 112. • Ruby based! •Very extensible! • Large number of extensions! • Simple client side installation $ gem install capistrano! Deployment Examples Capistrano / Capifony
- 113. set :application, "myapp"# Application name set :deploy_to, "/var/www/myapp" ! set :user, "deployer" set :use_sudo, false # sudo isn't required ! set :deploy_via, :remote_cache set :repository, "git@github.com:user/repo.git" ! role :web, "server.example.com",“server2.example.com” Deployment Examples Capistrano / Capifony
- 114. $ cap deploy:setup DeploymentExamples Capistrano / Capifony
- 115. ! |-- releases! `-- shared! |--logs! `-- uploads! Deployment Examples Capistrano / Capifony
- 116. $ cap deploy! $cap deploy:migrations! $ cap deploy:rollback! Deployment Examples Capistrano / Capifony
- 117. ! |-- current (symlinkto releases/20130112)! |-- releases! | `-- 20130112! `-- shared! |-- logs! `-- uploads! Deployment Examples Capistrano / Capifony
- 118.
- 119. Deployment Examples ! ! Define hostsin inventory file [webservers] foo.example.com bar.example.com www[01:50].example.com ! [dbservers] one.example.com two.example.com three.example.com
- 120. Deployment Examples ! ! Define tasks/ actions in playbook --- - hosts: webservers vars: http_port: 80 max_clients: 200 remote_user: root tasks: - name: ensure apache is at the latest version yum: pkg=httpd state=latest - name: write the apache config file template: src=/srv/httpd.j2 dest=/etc/httpd.conf notify: - restart apache - name: ensure apache is running
- 121. Deployment Examples ! ! Reuse taskswith Roles - hosts: webservers roles: - { role: servergrove.symfony2, symfony2_project_root: /var/www/vhosts/ example.com/, symfony2_project_name: demo, symfony2_project_branch: master , symfony2_project_release: 1 }
- 122. Deployment Examples ! ! Run process $ansible-playbook -i inventories/servers playbook.yml -v
- 123.
- 124. Deployment: Other options •Fabric (Python) • Idephix (PHP) • Magellanes (PHP) • Deployer (PHP) • Laravel / envoy (PHP) • Rocketeer (PHP)
- 125.
- 126. Packaging: fpm https://github.com/jordansissel/fpm Build packagesfor multiple platforms (deb, rpm, etc) with great ease and sanity. $ fpm -s dir -t rpm -n "myapp" -v 1.0 /var/www/myapp ! $ fpm -s dir -t deb -a all -n myapp -v 1.0 /etc/apache2/ conf.d/my.conf /var/www/myapp Deployment Complement Tools
- 127. App Metrics: StatsD& Graphite Deployment Complement Tools
- 128. App Metrics: liuggio/statsd-php-client DeploymentComplement Tools $ composer require liuggio/statsd-php-client:dev-master
- 129. App Metrics: liuggio/statsd-php-client DeploymentComplement Tools $sender = new SocketSender(/*'localhost', 8126, 'udp'*/); ! $client = new StatsdClient($sender); $factory = new StatsdDataFactory('LiuggioStatsdClientEntityStatsdData'); ! // create the data with the factory $data[] = $factory->timing('usageTime', 100); $data[] = $factory->increment('visitor'); $data[] = $factory->decrement('click'); $data[] = $factory->gauge('gaugor', 333); $data[] = $factory->set('uniques', 765); ! // send the data as array or directly as object $client->send($data);
- 130. App Metrics: liuggio/statsd-php-client DeploymentComplement Tools $data[] = $factory->timing('usageTime', 100);! ! // send the data as array or directly as object $client->send($data);
- 131. App Metrics: liuggio/statsd-php-client DeploymentComplement Tools $data[] = $factory->increment('orders');! ! // send the data as array or directly as object $client->send($data);
- 132. App Metrics: liuggio/statsd-php-client DeploymentComplement Tools $data[] = $factory->gauge('memory', 333);! ! // send the data as array or directly as object $client->send($data);
- 133. App Metrics: StatsD& Graphite Deployment Complement Tools App StatsD Graphite Grafana App App
- 134. Deployment Complement Tools AppMetrics: Grafana
- 135. Deployment Complement Tools AppMetrics: Grafana
- 136. Logging: Logstash Ship logsfrom any source, parse them, get the right timestamp, index them, and search them Deployment Complement Tools input { file { path => “/var/log/apache2/access_log” } } output { elasticsearch { host => localhost } }
- 137. Configure Apache tolog json LogFormat "{ "@timestamp": "%{%Y-%m-%dT %H:%M:%S%z}t", "@fields": { "client": "%a", "duration_usec": %D, "status": %s, "request": "%U%q", "method": "%m ", "referrer": "%{Referer}i" } }" logstash_json! ! ! # Write our 'logstash_json' logs to logs/ access_json.log! CustomLog logs/access_json.log logstash_json! Deployment Complement Tools Logging: Logstash
- 138. Configure Apache tolog json LogFormat "{ "@timestamp": "%{%Y-%m-%dT%H:%M:%S%z}t", "@fields": { "client": "%a", "duration_usec": %D, "status": %s, "request": "%U%q", "method": "%m", "referrer": "% {Referer}i" } }" logstash_json! ! ! # Write our 'logstash_json' logs to logs/access_json.log! CustomLog logs/access_json.log logstash_json! { "@timestamp": "2012-08-22T14:35:19-0700", "client": "127.0.0.1", "duration_usec": 532, "status": 404, "request": "/favicon.ico", "method": "GET", "referrer": "-" }! Result Deployment Complement Tools Logging: Logstash
- 139. Logging: Kibana Kibana isa user friendly way to view, search and visualize your log data Deployment Complement Tools
- 140. Logging: Kibana Kibana isa user friendly way to view, search and visualize your log data Deployment Complement Tools
- 141. Logging: Logstash +ElasticSearch + Kibana Deployment Complement Tools App / Logstash Redis Logstash filter/processor ElasticSearch Kibana App / Logstash App / Logstash
- 142.
- 143. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 144. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 145. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 146. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 147. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 148. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 149. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 150. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 151. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 152. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 153. Developer Tests build artifact Ansible Production GitHub JenkinsQA deploy Integration Tests Notifications Deployment Summary
- 154.
- 155.
- 156.
- 157.
- 158.
- 159. Now, we didfinish! ! Questions? Slides: http://slideshare.net/pgodel Twitter: @pgodel
- 160. Thank you! Slides: http://slideshare.net/pgodel Twitter:@pgodel https://joind.in/12199 Feedback please!