Building and Deploying PHP Applications, PHPTour 2016

BUILDING AND DEPLOYING PHP APPLICATIONS

MARTINS SIPENKO


ABOUT ME

▸ Located in Riga, Latvia

▸ Worked with IT since around 2002

▸ Lead engineer @KASKO, a fintech startup

▸ Student at University of Latvia

▸ AWS Certified


@MARTINSSIPENKO


SOME TERMINOLOGY


BUILD (VERB) PROCESS

▸ Transform which converts a code repo into an "executable" bundle known as a build


BUILD (NOUN)

▸ An artifact which is being produced during the build process that includes source code and compiled assets


DEPLOYMENT (VERB)

▸ Process of putting (deploying) the BUILD to servers

QA

Staging

Production


THE BUILD PROCESS


THE BUILD PROCESS

▸ Keep source code in version control

▸ Automatically generated things never are committed to version controlvendor/, node_modules/, generated JavaScript, CSS, documentation, etc..

▸ Continuous Integration configured to build each commit that is pushed to GitHub


QUICK TIP 1:

▸ Your project is kept in a known good state

▸ All developers operate on the same code-base

▸ Tests do not suddenly fail because of changes in one of its dependencies

ALWAYS COMMIT YOUR COMPOSER.LOCK FILE INTO YOUR SOURCE CODE REPOSITORY


WHAT HAPPENS DURING THE BUILD PROCESS?


1. INSTALL PROJECT DEPENDANCIES

composer install --optimize-autoloader --prefer-dist --no-interaction

npm install

bower install


2. STATIC CODE ANALYSIS

▸ codesniffer - coding standards

▸ phpmd - potential code issue detection

▸ phpcpd - duplicate code detection

▸ phploc - measure size of your project


3. TESTING

▸ Run unit testsphpunit

▸ Run "local" integration/acceptance testsphpunit, codeception, behat

▸ Testing frameworks can produce code coverage reports


4. COMPILE

▸ Bundle and minify JavaScript

▸ LESS/SASS -> CSS

▸ Optimize images

▸ Generate fonts from SVG

▸ Cache bust your static assets

▸ And many more...


5. CREATE BUILD PACKAGE

▸ a .tar.gz or .zip archive

▸ Only include things you need to run your application

▸ Exclude:

▸ things that were transformed into compiled assets (LESS, SASS, Coffee)

▸ .git

▸ node_modules/

▸ tests/

▸ ...


5. CREATE BUILD PACKAGE

$ rsync -a \ --exclude .git/ \ --exclude ./build/ \ --exclude node_modules/ \ --exclude tests/ \ --exclude vendor/phpunit/ \ --exclude .travis.yml \ --exclude .gitignore \ --exclude .env.example \ . /tmp/build-$BUILD_NUMBER

$ cd /tmp/build-$BUILD_NUMBER

$ tar -zcf /tmp/$REPO_NAME-$BUILD_NUMBER.tar.gz .


6. STORE BUILD PACKAGE

▸ Upload the build package to some storage

▸ AWS S3

▸ Dropbox

▸ NFS

▸ ...


QUICK TIP 2:

▸ Know which exact commit you have in the build

▸ Handy when you know the build number that is currently deployed to some environment

▸ You can check out and debug the code that was in particular build

TAG THE COMMIT WITH THE BUILD NUMBER AND PUSH THAT TAG TO GITHUB


OUTCOME: BUILD PACKAGE

▸ Can be deployed to any environment

▸ Does not change as you move it around

▸ Does not contain unnecessary assets

▸ Easy to download, and install


DEPLOYING THE BUILD


HOW DO YOU DEPLOY?


HOW TO DEPLOY?

▸ FTP

▸ SSH

▸ CRON

▸ 3rd party services

▸ custom solution


HOW TO DEPLOY?

▸ FTP

▸ SSH

▸ CRON

▸ Deployment Agent


DEPLOYMENT USING SSH

Pros:

▸ Easy to implement

▸ Rolling deployment possible

Cons:

▸ Needs access to server via SSH

▸ Needs to know location of each instance


DEPLOYMENT USING CRON

▸ CRON task that runs script every minute

▸ Script checks versions file stored somewhere (could also be S3)

▸ If required version differs from actual:

▸ download build package

▸ extract

▸ run post deployment hooks

▸ swap symlinks


DEPLOYMENT USING CRON

Pros:

▸ Fast

▸ Works well for small sites

▸ Easy to implement

Cons:

▸ No rolling deployment


DEPLOYMENT USING AGENT

▸ Agent runs on every instance

▸ Agent announces itself to centralized deployment tool

▸ Deployment tool orchestrates code deployments to every instance


DEPLOYMENT USING AGENT

Pros:

▸ Deployment does not require access via SSH

▸ Deployments are orchestrated so many strategies can be used: one by one, 50/50, all

Cons:

▸ Hard to implement


QUICK TIP 3:

▸ Humans make mistakes

▸ Works the same on each run

▸ Deployment scripts can be considered as documentation

▸ Less human time spent doing manual labor

AUTOMATE YOUR DEPLOYMENT PROCESS TO MAXIMUM


OTHER OPTIONS


OTHER OPTIONS

▸ Build VM Image (AMI) with code and software to run it

▸ Pro: Very robust,

▸ Con: but quite slow process

▸ Build Docker images

▸ Pro: Much faster and smaller than VM Images

▸ Con: Not really clear how to do automated deployments


SOME TOOLS


CONTINUOUS INTEGRATION (CI)

▸ Hosted (SaaS)

▸ TravisCI

▸ CircleCI

▸ CodeShip

▸ ...

▸ Self hosted

▸ Jenkins

▸ Bamboo

▸ ...


CODE DEPLOYMENT

▸ 3rd party

▸ AWS CodeDeploy

▸ CodeShip

▸ ...

▸ Capistrano

▸ Fabric

▸ Custom


QUICK TIP 4:

▸ Application should use environment variables for configuration

▸ Values of env variables are different for in environment

▸ Env vars are easy to change between deploys without changing any code

DO NOT PUT ANY CONFIG IN GIT OR BUILD PACKAGE


QUICK TIP 5:

READ THIS BOOK!CONTINUOUS DELIVERY Jez HumbleDavid Farley


Q&A?


MERCI!

https://joind.in/talk/[email protected]@gmail.com


PLEASE GIVE FEEDBACK

https://joind.in/talk/[email protected]@gmail.com

Technology

Building and Deploying PHP Applications, PHPTour 2016