Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A modern approach to PHP development

A modern approach to PHP development

There have been some great advancements in the PHP ecosystem in the last couple years. Come learn about two tools that could make your projects more productive and enjoyable. The first is Composer, a modern dependency manager for PHP. The second is Silex, a small, lightweight framework that gets out of your way, but also gives you a great upgrade path as your needs change and grow over time. I will also discuss Vagrant, a great tool for provisioning a reliable development environment for you and your team.

Joel Clermont

August 12, 2013
Tweet

More Decks by Joel Clermont

Other Decks in Programming

Transcript

  1. A modern approach to
    PHP development
    Joel Clermont
    @jclermont
    Tuesday, August 13, 13
    No bio slide. If you want to know more about me personally, we can discuss over a beer at Happy Hour tonight.

    View full-size slide

  2. Platinum Sponsors
    Gold Sponsors
    Tuesday, August 13, 13

    View full-size slide

  3. Goals
    Tuesday, August 13, 13
    I only have one hour. In order to be effective, we need to establish some clear goals up front.

    View full-size slide

  4. Goals
    • Expose you to some new ideas and tools
    Tuesday, August 13, 13
    Not a dry “how to do X” technical discussion. There will be some “how”, but focus on the “why”

    View full-size slide

  5. Goals
    • Expose you to some new ideas and tools
    • Show you how they solved problems for me
    Tuesday, August 13, 13
    Odds are, you have faced (or are facing) some of the same problems.
    No solution is “one size fits all” - so take the knowledge and apply it in your specific project, team and organization

    View full-size slide

  6. Goals
    • Expose you to some new ideas and tools
    • Show you how they solved problems for me
    • Get you interested enough to try it out later
    Tuesday, August 13, 13
    I believe that the topics we cover today can make you more efficient, produce higher quality code and make your development more FUN.
    To me, less frustration == more fun.

    View full-size slide

  7. What do I mean by modern?
    Tuesday, August 13, 13
    Simplest definition: something newer than what you are currently doing. (tool, library, technique, language feature, etc)

    View full-size slide

  8. ¬ (Newer 㱺 Better)
    Tuesday, August 13, 13
    Translation: Newer isn’t always better. (I love Unicode characters)
    The Art of Computer Programming is a classic example. These books are decades old but still extremely valuable.
    Developers tend to like shiny things. We often jump on new tools and technologies
    But newer isn’t always better. Remember previous disclaimer: I found these newer techniques better in my experience. YMMV

    View full-size slide

  9. Three talks for the price of one!!
    Tuesday, August 13, 13
    Structure will be 3 topics under one central theme
    I will pause for questions at the end of each section, but don’t wait. Interrupt me at any time (clarification, disagreement, etc)
    Interaction makes the presentation more enjoyable for me and more valuable for you.

    View full-size slide

  10. PROBLEM
    Wasting time setting up or maintaining a
    local dev environment
    Tuesday, August 13, 13
    Option 1: NO local env. Edit and upload. Test on server (ouch)
    Option 2: OS X, use system apache/php/mysql (issues upgrading, configuring)
    Option 3: packaged env like MAMP. Pretty good, but leads to a second problem . . .

    View full-size slide

  11. PROBLEM
    “Works on my machine!”
    Tuesday, August 13, 13
    Dev environment doesn’t match others on the team. Doesn’t match production
    Scenario: You’re running MAMP on OS X, everything works. Upload to production (Linux), getting 404 errors on some pages. Files exist.
    What happened?

    View full-size slide

  12. Solution
    Tuesday, August 13, 13
    January 2010
    Solves the issue of time/effort to setup and maintain your local environment
    Eliminates inconsistencies between team environments AND production environment
    Best of all, it doesn’t require you to force people to give up their favorite OS or text editor/IDE

    View full-size slide

  13. Uses virtual machines
    portable, isolated, project-specific
    Tuesday, August 13, 13
    runs on any major OS
    doesn’t mess with stock libraries
    one project can be Nginx with 5.5, other can be Apache with 5.3

    View full-size slide

  14. FREE
    Tuesday, August 13, 13
    nominal cost if you want to use the VMWare infrastructure instead of VirtualBox
    all the tools I mention are free. Can’t beat the price.

    View full-size slide

  15. DEMO
    Tuesday, August 13, 13
    maybe this all sounds a little too good to be true
    demo with Drupal (many OSS projects are distributing Vagrant configs for easy setup/testing)
    ~/vagrant/drupal

    View full-size slide

  16. Pick a “box”
    Tuesday, August 13, 13
    Minimum configuration is picking a base box: usually a flavor of Linux
    Vagrant provides several common choices, Community provides many, many others
    You can even create your own

    View full-size slide

  17. Side note: disk space
    Tuesday, August 13, 13
    You might be wondering about how much space all these VMs are going to take?
    Vagrant stores one copy of each base box
    Project has its own copy
    Most Linux VMs are 200 - 400 MB, not a huge impact

    View full-size slide

  18. vagrant  init
    Tuesday, August 13, 13
    this creates your Vagrantfile
    really a Ruby file - don’t despair if you don’t know Ruby
    check it into source control

    View full-size slide

  19. vagrant  up
    Tuesday, August 13, 13
    boots the machine
    no GUI, saves on resources

    View full-size slide

  20. vagrant  ssh
    Tuesday, August 13, 13
    kick the tires, get full access to the VM, just like any server

    View full-size slide

  21. Oh no, do I have to use vim or emacs?
    Tuesday, August 13, 13
    Remember, I said you didn’t have to give up your text editor or IDE of choice
    ssh is available, but there is a better way to edit files
    your project folder is sync’d into the VM at /vagrant
    anything you do in the host is sync’d to the VM
    if performance is an issue, NFS is an option (except on Windows)

    View full-size slide

  22. vagrant  suspend
    vagrant  halt
    Tuesday, August 13, 13

    View full-size slide

  23. vagrant  destroy
    Tuesday, August 13, 13
    Nothing is really lost when you do destroy. It will simply rebuild the box from your Vagrantfile
    Project code and data lives in your host OS

    View full-size slide

  24. How do I configure my VM?
    Tuesday, August 13, 13
    Remember, how I mentioned that your Vagrantfile is really a Ruby file?
    Vagrant has concept of provisioners: Chef / Puppet - learning curve
    Shell scripts: works, but can be a bit clunky and repetitive
    Ansible: declarative approach, but still has some learning curve

    View full-size slide

  25. PuPHPet == awesome
    Tuesday, August 13, 13
    awkwardly named, but incredibly useful
    under the hood, it uses Puppet, but you configure it with a web UI
    if you want to learn Puppet, studying the manifests from PuPHPet is a great way to start

    View full-size slide

  26. References
    • Vagrant http://www.vagrantup.com
    • Drupal Vagrant box https://drupal.org/project/vagrant
    • Vagrant commands for the lazy and forgetful: http://codepoets.co.uk/
    2013/vagrant-commands-for-the-lazy-and-forgetful/
    • PuPHPet https://puphpet.com
    Tuesday, August 13, 13

    View full-size slide

  27. Questions?
    Tuesday, August 13, 13

    View full-size slide

  28. PROBLEM
    Managing project dependencies
    is time-consuming and error prone
    Tuesday, August 13, 13
    download a zip file?
    clone a git repo?
    PEAR
    PHAR files

    View full-size slide

  29. PROBLEM
    Vendor code is mixed in with your code
    Tuesday, August 13, 13
    .gitignore files work, maybe git submodules. requires discipline

    View full-size slide

  30. Solution
    Tuesday, August 13, 13
    Composer makes it easy to declare your dependencies per project
    AND to keep them up to date (this part can be the trickiest over time)

    View full-size slide

  31. Dependencies, not packages
    Tuesday, August 13, 13
    Easy mistake to make, I even made it in my talk abstract
    packages are system-level, composer is project-level by default (can be used to install global packages)
    conceptually very similar to Ruby’s bundler or Node’s npm

    View full-size slide

  32. Easily specify a dependency level
    Tuesday, August 13, 13
    what version of a library do you want?
    only master/production? dev ok? dev tools?
    it knows about your dependency’s dependencies (down the rabbit hole)

    View full-size slide

  33. How paranoid are you?
    $ curl -s https://getcomposer.org/installer | php
    Tuesday, August 13, 13
    The installation instructions take curl output and pipe it into your php executable
    YOLO
    i recommend installing it globally in your path
    no need to manage the composer code per project

    View full-size slide

  34. composer.json
     {
    "minimum-­‐stability":  "dev",  
    "require":  {
    "silex/silex":  "1.0.*",
    "doctrine/dbal":  ">=2.2",
    "knplabs/console-­‐service-­‐provider":  ">=1.0.0",
    "igorw/config-­‐service-­‐provider":  "*.*.*"
    }
             }
    Tuesday, August 13, 13

    View full-size slide

  35. composer  install
    Tuesday, August 13, 13
    looks at composer.json and installs dependencies
    puts everything in a /vendor folder (easy to exclude from your git repo)
    creates a composer.lock file (snapshot of what was just installed)
    commit composer.json and composer.lock to repo
    if composer.lock is present, .json file is ignored and snapshot in .lock is installed

    View full-size slide

  36. Use your dependencies painlessly
    require  'vendor/autoload.php'
    Tuesday, August 13, 13
    install also builds an autoload file for you
    one single point of entry to all your composer managed code

    View full-size slide

  37. composer  update
    Tuesday, August 13, 13
    follows rules in composer.json, but updates as far as possible while following rules
    sidebar on semantic versioning

    View full-size slide

  38. Tuesday, August 13, 13
    the real power of composer
    no need to tell composer where to fetch each package
    14,454 packages registered

    View full-size slide

  39. Is Packagist the only way?
    Tuesday, August 13, 13
    you can specify a git (or other VCS) repo in composer.json
    if the package isn’t composer aware, you can autoload it if it supports PSR-0
    if package isn’t PSR-0, use a classmap
    there is always a way

    View full-size slide

  40. composer  create-­‐project
    Tuesday, August 13, 13
    Will do a demo later on Silex
    Basic way to install a framework, CMS, etc with one command

    View full-size slide

  41. Bonus points:
    create your own packages
    Tuesday, August 13, 13
    you can publish to Packagist
    host your own internal Packagist
    or lighter weight tool called Satis

    View full-size slide

  42. References
    • Composer http://getcomposer.org
    • Packagist https://packagist.org
    • Satis https://github.com/composer/satis
    • Semantic versioning http://semver.org
    Tuesday, August 13, 13

    View full-size slide

  43. Questions?
    Tuesday, August 13, 13

    View full-size slide

  44. PROBLEM
    Ad-hoc project organization
    lacks structure
    Tuesday, August 13, 13
    300 PHP files in your public web root
    I’m sure you’ve never done that

    View full-size slide

  45. PROBLEM
    Lots of repeated or boilerplate code
    Tuesday, August 13, 13
    content negotiation: should I send HTML or JSON back?
    setting cache directives
    introspecting the HTTP request

    View full-size slide

  46. PROBLEM
    Automated testing is hard
    Tuesday, August 13, 13
    500+ line functions
    lots of side effects
    extremely high cyclomatic complexity (fancy way of saying there are too many paths through your code)

    View full-size slide

  47. Solution
    Tuesday, August 13, 13
    MicroPHP Manifesto: January 2012
    This could be an hour-long talk on its own, or even a full day workshop
    You aren’t going to learn how to use Silex, but why a micro framework is worth considering
    Silex is only one option: Slim is another great one. I’m sure there are others

    View full-size slide

  48. Why a framework?
    Tuesday, August 13, 13
    It can enforce some structure on your project and make it a lot easier to avoid the big ball of mud
    You can still write complex, untestable, disorganized code with a framework.

    View full-size slide

  49. Why a micro framework?
    Tuesday, August 13, 13
    Micro PHP manifesto
    Zend and Symfony (full stack) can be useful, but have steeper learning curve. Require higher team buy-in
    Micro-frameworks can fit almost any type of project
    I’m a fan of SOA, many single-focused services coordinating together
    YMMV

    View full-size slide

  50. DEMO
    Tuesday, August 13, 13
    Common complaint: too hard to get started
    composer create-project fabpot/silex-skeleton silex-demo
    leverage both composer and vagrant

    View full-size slide

  51. Simple routing
    Tuesday, August 13, 13

    View full-size slide

  52. Logic before each request
    Tuesday, August 13, 13

    View full-size slide

  53. Automated testing
    Tuesday, August 13, 13

    View full-size slide

  54. References
    • Silex http://silex.sensiolabs.org
    • Pimple http://pimple.sensiolabs.org
    • Micro manifesto http://microphp.org
    Tuesday, August 13, 13

    View full-size slide

  55. Questions?
    Tuesday, August 13, 13

    View full-size slide

  56. Please TRY this on your own
    Tuesday, August 13, 13
    There will be some learning curve but remember the goals: more efficient, higher quality code, have more fun while developing

    View full-size slide

  57. August 11th – 13th 2014
    Same Place, Same Time
    Tuesday, August 13, 13
    Go tell all your fellow PHP devs about next year. I would like to see even more PHP topics and attendees next year.
    If you think of more questions, find me later or tweet me @jclermont. I’m here all three days

    View full-size slide