PFCongres 2012 - Rock Solid Deployment of PHP Apps

Rock Solid Deployment
of PHP Applications
Pablo Godel @pgodel - www.pfcongres.com
Sep 15th 2012 - Utrecht, NL
https://joind.in/7079

Saturday, September 15, 2012

Who Am I?

⁃ Born in Argentina, living in the US since 1999
⁃ PHP & Symfony developer
⁃ Founder of the original PHP mailing list in spanish
⁃ Master of the parrilla


ServerGrove!

⁃ Founded ServerGrove Networks in 2005

⁃ Provider of web hosting specialized in PHP,
Symfony, ZendFramework, MongoDB and others

⁃ Servers in USA and Europe!


Community is our teacher
⁃ Very active open source supporter through code
contributions and usergroups/conference sponsoring


Deployment

?

Deployment
Software deployment is all of the activities that make
a software system available for use.

http://en.wikipedia.org/wiki/Software_deployment

Deployment

A very important part of
the application life-cycle


Deployment

A very important critical part
of the application life-cycle


Deployment

It should not be an
after thought


Deployment

It should be predictable


Deployment

The more you do it the
better it goes


Deployment: Goals


Deployment: Goals

One-click deploys


Deployment: Goals

One-click deploys
Continuous deploys


PHP Apps
Deployment


Deployment: Goals

Anytime & Anywhere


Deployment: Goals

Anyone


Deployment: Goals

Reliable


Deployment: Goals

Rollbacks


Deployment: Goals

No downtime


Deployment: Goals

Reusable


Deployment: Goals

Scalable


Deployment: Goals

• One-click / continuous deploys
• Anytime & Anywhere
• Anyone
• No downtime
• Predictable & Reliable
• Rollbacks
• Reusable
• Scalable


Deployment Facts


Deployment: Fact #1

Deployment starts with the developer

• Setup development environment to be as close
as possible to productions servers
• Setup test/qa/staging servers
• Use Vagrant to manage VMs
• Use Puppet/Chef to manage OS packages/
conﬁguration


Deployment: Fact #2

Success linked to server OS setup

• Use Puppet/Chef to manage OS packages/
conﬁguration
• Create OS packages for 3rd party software
• Setup your own package repositories


Deployment: Fact #3

Monitoring is uptime

• Use monitoring tools to know what is going on
with your servers (Ganglia, Cacti, Zabbix, etc.)
• Add monitoring and metrics to your app
(Graphite, StatsD, New Relic)
• Use your logs wisely (Graylog, Logstash, Kibana)


Deployment Methodologies


Deployment Methodologies

• VIM-style
• FTP uploads
• rsync
• source control (svn, git)
• Build tools (ant, phing)
• Specialized tools (capistrano, fabric, etc)
• Package based (rpm, deb, etc)


Web Apps Deployment:
Steps overview


First time

• Copy files to server(s)
• Set server-side configurations
• Load DB fixtures
• Process and install assets
• Warm up cache
• “Enable” site


Subsequent times

• Copy ﬁles to server(s)
• Apply DB updates (migrations)
• Process and install assets
• Warm up cache
• “Enable” site


Deployment: Challenges



Challenge:
Fast & reliable copy of ﬁles

Solutions:
• rsync
• git pull
• setup git repo on local network to save
bandwidth and avoid issues if git server is down
(i.e. github)



Challenge:
Scalable

Solutions:
• use a tool that allows to go from 1 to n servers
easily (i.e. capistrano)
• pssh allows to send commands to n servers in
parallel
• package your app in OS packages
like .rpm/.deb to easily install across n servers


Challenge:
Rollbacks

Solutions:
• test!
• tag releases
• dedicated branches (master for production)
• deploy each release in its own directory



Challenge:
Secure

Solutions:
• use ssh based connections
• donʼt store passwords on source control
• store sensitive strings (passwords) in server
environment variables



Challenge:
DB migrations

Solutions:
• Doctrine Migrations
• Consider document oriented DBs like
MongoDB

“The best migrations are the ones you don’t have to do”



Challenge:
Static assets

Solutions:
• YUICompress shrinks JS and CSS ﬁle sizes
• Enable web server compression
• Add versioning to static assets links (code.js?v=1)
• Assetic combines multiple ﬁles into one
• Run utilities locally or in a staging server, deploy
result


Challenge:
Caching

Solutions:
• Update one server while others handle load
• Group servers and update group at a time
• execute commands on “ﬁnalize” to clear up APC
cache



Challenge:
File permission conﬂicts

Solutions:
• 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


PHP Apps Deployment:
Other common pitfalls


Other common pitfalls
• Case sensitive ﬁlesystems
• Conﬁguration 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

Examples


Examples
Simplest continuous deployment ever!
hook.php
<?php

exec(ʻ/usr/bin/env -i HOME=/var/www git pullʼ);
echo “All done!”;

screenshot


Examples
Capistrano

• Ruby based
• Very extensible
• Large number of extensions
• Simple client side installation

$ gem install capistrano


Examples
Capistrano

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”


Examples
Capistrano

$ cap deploy
$ cap deploy:migrations
$ cap deploy:rollback


Examples
Capifony (Symfony2)

• Extension of Capistrano
• Implements lots of needed features
for Symfony
• Great documentation


Examples
Capifony (Symfony2)

$ capifony .


Examples
Capifony (Symfony2)
set :keep_releases, 3

# directories that will be shared between all deployments
set :shared_children, [ app_path + "/logs", web_path + "/
uploads"]

set :update_vendors, true
# set :use_composer, true

set :dump_assetic_assets, true


Examples
Capifony (Symfony2)

$ cap deploy:setup


Examples
Capifony (Symfony2)

|-- httpdocs
| `-- index.php
|-- releases
`-- shared
|-- logs
`-- uploads

5 directories, 1 ﬁle

Examples
Capifony (Symfony2)

$ cap deploy
$ cap deploy:migrations
$ cap deploy:rollback


Other options

• Fabric
• WePloy
• Phing
• Magallanes
• Jenkins


Tools


Tools
App Metrics: StatsD & Graphite


Tools
Logging: Logstash
Ship logs from any source, parse them, get the right
timestamp, index them, and search them


Tools
Logging: Logstash
Conﬁgure 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": "-" }


Tools
Logging: Graylog


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


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


Time for demo


Summary


•Stop using FTP


•Stop using FTP
•Plan early


•Stop using FTP
•Plan early
•Practice


•Stop using FTP
•Plan early
•Practice
•Monitor


•Stop using FTP
•Plan early
•Practice
•Monitor
•AUTOMATE!


Thank you!
QUESTIONS?

Rate Me Please! https://joind.in/7079
Slides: http://slideshare.net/pgodel
Twitter: @pgodel
E-mail: pablo@servergrove.com

PFCongres 2012 - Rock Solid Deployment of PHP Apps

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (20)

Similaire à PFCongres 2012 - Rock Solid Deployment of PHP Apps

Similaire à PFCongres 2012 - Rock Solid Deployment of PHP Apps (20)

Plus de Pablo Godel

Plus de Pablo Godel (20)

Dernier

Dernier (20)

PFCongres 2012 - Rock Solid Deployment of PHP Apps