Web applications are becoming increasingly more complex, so deployment is not just transferring files with FTP anymore. We will go over the different challenges and how to deploy our PHP applications effectively, safely and consistently with the latest tools and techniques. We will also look at tools that complement deployment with management, configuration and monitoring.

1. Photo: Alvaro Videla
Rock Solid
Deployment
of Symfony
Applications
Pablo Godel @pgodel
Photo by @old_sound
https://joind.in/12960

2. Hi, I am Pablo.

3. Hi, I am Pablo.
!
@pgodel

6. A GUIDING LIGHT FOR STUDENT SUCCESS

7. A GUIDING LIGHT FOR STUDENT SUCCESS
Symfony2 + AngularJS + much more!

8. A GUIDING LIGHT FOR STUDENT SUCCESS
We are Hiring!

9. Deployment ?

10. Deployment
Software deployment is all of the activities that !
make a software system available for use.
http://en.wikipedia.org/wiki/Software_deployment

11. Deployment
A very important part of
the application life-cycle

12. Deployment
A very important critical part
of the application life-cycle

13. Deployment
It should not be an !
after thought

14. Deployment
It should be predictable

15. Deployment
The more you do it the
better it goes

20. Deployment in
the PaaS era

21. 1. Open an account

22. 2. Create app

23. 3. Push code

24. 4. Voilà!

26. composer.json !
!
Procfile

27. $ heroku create!

28. $ git push heroku master!

30. $ heroku ps:scale web=5!

31. That’s it! ;-)

32. Questions?
Slides: http://slideshare.net/pgodel
Twitter: @pgodel

33. But…

34. Deployment for
the rest of us

35. Deployment Goals

36. Deployment Goals
One-click deploys

37. Deployment Goals
One-click deploys

38. Deployment Goals
Continuous deploys

39. Deployment Goals
Continuous deploys

40. Deployment Goals
Anytime & Anywhere

41. Deployment Goals
Anytime & Anywhere

42. Anyone
Deployment Goals

43. Anyone
Deployment Goals

44. Reliable
Deployment Goals

45. Reliable
Deployment Goals

46. Rollbacks
Deployment Goals

47. Rollbacks
Deployment Goals

48. No downtime
Deployment Goals

49. No downtime
Deployment Goals

50. Reusable
Deployment Goals

51. Reusable
Deployment Goals

52. Reusable
Deployment Goals

53. Scalable
Deployment Goals

54. Scalable
Deployment Goals

55. Deployment Facts

56. Deployment Fact #1
Deployment starts with the developer

57. Deployment Fact #1
Deployment starts with the developer
• Development environment must be as close as
possible to productions servers!

58. Deployment Fact #1
Deployment starts with the developer
• Development environment must be as close as
possible to productions servers!
• Setup test/qa/staging servers!

59. Deployment Fact #1
Deployment starts with the developer
• Development environment must be as close as
possible to productions servers!
• Setup test/qa/staging servers!
• Use Vagrant to manage VMs!

60. Deployment Fact #1
Deployment starts with the 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!

61. Deployment Fact #1
Deployment starts with the 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)

62. Deployment Fact #2
Success depends on server OS setup

63. Deployment Fact #2
Success depends on server OS setup
• Automate installation/configuration with Ansible/
Puppet/Chef !

64. Deployment Fact #2
Success depends on server OS setup
• Automate installation/configuration with Ansible/
Puppet/Chef !
• Create OS packages for 3rd party software

65. Deployment Fact #2
Success depends on server OS setup
• Automate installation/configuration with Ansible/
Puppet/Chef !
• Create OS packages for 3rd party software!
• Setup your own package (rpm/deb) repositories

66. Deployment Fact #3
Monitoring is uptime

67. Deployment Fact #3
Monitoring is uptime
• Use tools to know what is going on with your
servers (Ganglia, Cacti, Zabbix, etc.)!

68. Deployment Fact #3
Monitoring is uptime
• Use tools to know what is going on with your
servers (Ganglia, Cacti, Zabbix, etc.)!

69. Deployment Fact #3
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)!

70. Deployment Fact #3
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)

71. Deployment Methodologies

72. Deployment Methodologies
• VIM-style

73. Deployment Methodologies
• VIM-style!
• FTP uploads

74. Deployment Methodologies
• VIM-style!
• FTP uploads

75. Deployment Methodologies
• VIM-style!
• FTP uploads!
• Rsync

76. Deployment Methodologies
• VIM-style!
• FTP uploads!
• Rsync!
• Source control (GIT, SVN)

77. Deployment Methodologies
• VIM-style!
• FTP uploads!
• Rsync!
• Source control (GIT, SVN)!
• Build tools (Ant, Phing, Jenkins)!

78. Deployment Methodologies
• VIM-style!
• FTP uploads!
• Rsync!
• Source control (GIT, SVN)!
• Build tools (Ant, Phing, Jenkins)!
• Package based (RPM, DEB, …) !

79. Deployment Methodologies
• VIM-style!
• FTP uploads!
• Rsync!
• Source control (GIT, SVN)!
• Build tools (Ant, Phing, Jenkins)!
• Package based (RPM, DEB, …) !
• Specialized tools (Capifony, Deployer, …)!

80. 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, …)

81. Deployment: Steps overview

82. Deployment: First time
• Copy files to server(s)!
• Set server-side configurations!
• Load DB fixtures!
• Process and install assets!
• Warm up cache!
• Enable site

83. 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

84. We can automate!

85. Deployment Challenges

86. Deployment Challenges
Challenge: Secure

87. Deployment Challenges
Challenge: Secure
• use ssh based connections!

88. Deployment Challenges
Challenge: Secure
• use ssh based connections!
• don’t store passwords on source control

89. Deployment Challenges
Challenge: Secure
• use ssh based connections!
• don’t store passwords on source control!
• use environment variables for sensitive data

90. Deployment Challenges
Challenge: Static assets

91. Deployment Challenges
Challenge: Static assets
• Minimize/combine JS and CSS files!

92. Deployment Challenges
Challenge: Static assets
• Minimize/combine JS and CSS files!
• Enable web server compression!

93. Deployment Challenges
Challenge: Static assets
• Minimize/combine JS and CSS files!
• Enable web server compression!
• Add versioning to static assets links (code.js?v=1)!

94. Deployment Challenges
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!

95. Deployment Challenges
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

96. Deployment Challenges
Challenge: File permission conflicts

97. Deployment Challenges
Challenge: File permission conflicts
• Run Apache/PHP with same user!

98. Deployment Challenges
Challenge: File permission conflicts
• Run Apache/PHP with same user!
• Use php-fpm instead of mod_php!

99. Deployment Challenges
Challenge: File permission conflicts
• Run Apache/PHP with same user!
• Use php-fpm instead of mod_php!
• Create “deploy” user and add web server to the
group

100. Deployment Challenges
Challenge: File permission conflicts
• 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!

101. Deployment Challenges
Challenge: File permission conflicts
• 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

102. Common Pitfalls

103. Common Pitfalls
• Case sensitive filesystems!

104. Common Pitfalls
• Case sensitive filesystems!
!
src/Acme/ClassName !
!= !
src/Acme/Classname.php

105. Common Pitfalls
• Case sensitive filesystems!
!
src/Acme/ClassName !
!= !
src/Acme/Classname.php

106. Common Pitfalls
• Case sensitive filesystems!
• Configuration differences!

107. Common Pitfalls
• Case sensitive filesystems!
• Configuration differences!
• Outdated 3rd party software

108. Common Pitfalls
• Case sensitive filesystems!
• Configuration differences!
• Outdated 3rd party software!
• Github down

109. Common Pitfalls
• Case sensitive filesystems!
• 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

110. Common Pitfalls
• Case sensitive filesystems!
• Configuration differences!
• Outdated 3rd party software!
• Github down

111. Deployment Examples

112. Deployment Examples
Simplest continuous deployment ever!
hook.php
<?php !
!
exec(‘/usr/bin/env -i HOME=/var/www git pull’);!
echo “All done!”;

113. Simplest continuous deployment ever!
hook.php
Deployment Examples
<?php !
!
exec(‘/usr/bin/env -i HOME=/var/www git pull’);!
echo “All done!”;
GitHub hook
screenshot

114. Deployment Examples
Capistrano!
!
+ !
!
Capifony

115. Deployment Examples
Capistrano / Capifony
• Ruby based!
• Very extensible!
• Large number of extensions!
• Simple client side installation

116. Deployment Examples
Capistrano / Capifony
• Ruby based!
• Very extensible!
• Large number of extensions!
• Simple client side installation
$ gem install capifony!

117. Deployment Examples
Capistrano / Capifony
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”

118. Deployment Examples
Capistrano / Capifony
$ cap deploy:setup

119. Deployment Examples
Capistrano / Capifony
!
|-- releases!
`-- shared!
|-- logs!
`-- uploads!

120. Deployment Examples
Capistrano / Capifony
$ cap deploy!
$ cap deploy:migrations!
$ cap deploy:rollback!

121. Deployment Examples
Capistrano / Capifony
!
|-- current
(symlink to releases/20130112)!
|-- releases!
| `-- 20130112!
`-- shared!
|-- logs!
`-- uploads!

122. Deployment Examples
Deploying with

123. 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

124. 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

125. Deployment Examples !
!
Reuse tasks with 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
}

126. Deployment Examples
!
!
Run process
$ ansible-playbook -i inventories/servers
playbook.yml -v

127. Deployment Examples
!
!
Run process

128. Deployment: Other options
• Fabric (Python)
• Idephix (PHP)
• Magellanes (PHP)
• Deployer (PHP)
• Laravel / envoy (PHP)
• Rocketeer (PHP)

129. Deployment Complement Tools

130. Deployment Complement Tools
Packaging: fpm
Build packages for 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
https://github.com/jordansissel/fpm

131. Deployment Complement Tools
App Metrics: StatsD & Graphite

132. Deployment Complement Tools
App Metrics: liuggio/statsd-php-client
$ composer require liuggio/statsd-php-client

133. Deployment Complement Tools
App Metrics: liuggio/statsd-php-client
$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);

134. Deployment Complement Tools
App Metrics: liuggio/statsd-php-client
$data[] = $factory->timing('usageTime', 100);!
!
// send the data as array or directly as object
$client->send($data);

135. Deployment Complement Tools
App Metrics: liuggio/statsd-php-client
$data[] = $factory->increment('orders');!
!
// send the data as array or directly as object
$client->send($data);

136. Deployment Complement Tools
App Metrics: liuggio/statsd-php-client
$data[] = $factory->gauge('memory', 333);!
!
// send the data as array or directly as object
$client->send($data);

137. Deployment Complement Tools
App Metrics: StatsD & Graphite
App
App App
StatsD Graphite
Grafana

138. Deployment Complement Tools
App Metrics: Grafana

139. Deployment Complement Tools
App Metrics: Grafana

140. Deployment Complement Tools
Logging: Logstash
Ship logs from any source, parse them, get the right
timestamp, index them, and search them
input {
file {
path => “/var/log/apache2/access_log”
}
}
output {
elasticsearch {
host => localhost
}
}

141. Deployment Complement Tools
Logging: Logstash
Configure Apache to log 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!

142. Deployment Complement Tools
Logging: Logstash
Configure Apache to log 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!
Result
{ "@timestamp": "2012-08-22T14:35:19-0700", "client": "127.0.0.1",
"duration_usec": 532, "status": 404, "request": "/favicon.ico",
"method": "GET", "referrer": "-" }!

143. Deployment Complement Tools
Logging: Kibana
Kibana is a user friendly way to view, search and visualize
your log data

144. Deployment Complement Tools
Logging: Kibana
Kibana is a user friendly way to view, search and visualize
your log data

145. Deployment Complement Tools
Logging: Logstash + ElasticSearch + Kibana
App / Logstash
App / Logstash App / Logstash
Redis Logstash
filter/processor
ElasticSearch Kibana

146. Deployment Summary

147. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

148. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

149. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

150. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

151. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

152. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

153. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

154. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

155. Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications
Deployment Summary

156. Deployment Summary
Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications

157. Deployment Summary
Developer Tests
build artifact
GitHub
Jenkins QA deploy
Integration
Tests
Ansible Production
Notifications

158. Deployment Future

159. Deployment Future
Containers

160. Deployment Future
Docker
Web App
Apache / PHP
Linux

161. Deployment Future
Docker
Host
Docker client
C
VM
Web
Server
C C
DB
Server
App
Server

162. Docker
Deployment Future
Host
Docker client
C
VM
Web
Server
C C
DB
Server
App
Server

163. Docker
Deployment Future
Host
Docker client
C
VM
Web
Server
C C
DB
Server
App
Server

164. Docker
Deployment Future
Host
Docker client
C
VM
Web
Server
C C
DB
Server
App
Server
Host
C
VM
Web
Server
C C
DB
Server
App
Server

165. Docker
Deployment Future
Host
Docker client
C
VM
Web
Server
C C
DB
Server
App
Server
Host
C
VM
Web
Server
Host
C C
DB
Server
C C
App
Server
C
Web
Server
DB
Server
App
Server
Docker
Kernel

166. Final Thoughts

167. Stop using FTP

168. Plan early

169. Practice

170. Monitor

171. AUTOMATE!

172. Now, we did finish!
!
Questions?

173. Feedback Please!
https://joind.!
in/12960
!
http://slideshare.net/pgodel
@pgodel

174. Feedback Please!
https://joind.!
in/12960
!
Thank you!
http://slideshare.net/pgodel
@pgodel