Intro To PHP


To teach you PHP we are going to use a "Real World" example. You've decided to create a voting system for you and your friends to play with. You've decided at a minimum, you'd like to allow users to:

  • view the topics sorted by number of votes
  • vote on topics
  • create, edit, and destroy topics

You've sketched up an initial screenshot of what you want it to look like:



When you have completed today's goal of getting the basic application online you should understand:

  • Basic PHP syntax
  • How to try your PHP code (Psy Shell)
  • How to go from requirements to a new working web application
  • How to get your application online
  • The basic tools a web developer uses (source control, editor, console, local server)


  • 1-ish hour of introduction to the language
  • 5-ish hours of building your application

This is just a rough guideline, not a mandate. Some steps you'll go over and some you'll go under. It'll all work out by the end of the day...


We're going to be working with:

  • PHP
  • MySQL Database Server
  • Terminal
  • Bootstrap 3
  • Sublime Text Editor
  • Psysh
  • Vagrant & VirtualBox
  • Ubuntu Linux

We will provide you with everything you need to get started on the day.

Working Effectively and Efficiently

We highly recommend you do the following:

  • Open your browser fresh or hide any windows you already have open.
    • Bring up one window with two tabs
    • One for this content
    • One for interacting with your app.
  • Open your text editor and do not ever close it. We're not quitters.
  • When we get to the Terminal, you'll want to keep that open too
  • Hide all extra applications. Turn off twitter, IM, and all other distractions.

By minimizing the number of things you interact with, you reduce the amount of time spent switching between them and the context lost as you work through the lessons. Having 50 tabs open in your web browser gets confusing and wastes time.


Each lesson will look like this:

Step Title


Description of the current step.

Red because big goals are scary


 Step 1

Commands to run, or code to write

Yellow because we've gotten it done, but we have no clue what's going on.


Details of what the steps actually did... spell out the cause and effect.

Green because we can tie everything together now.

Next Step: