Skip to main content

Using PHP and Git-based Deployment on Heroku without Facebook Apps


Getting PHP up and running on Heroku is easy. Although you can easily deploy PHP applications on your own traditional web hosting provider (Monster Hosting, 1&1 Hosting), PHPFog, or Windows Azure, in this blogpost, we quickly go through how to get up and running on Heroku.

Just before going into it, a while ago, there was a partnership announced between Facebook and Heroku. As an application developer, if you wanted a place (for free) to deploy your social application, you could use Heroku -- and you would have a lot of automation behind setting up your canvas/tab configuration. This was back in the day when they had Page Tabs!

Traditionally, developers would use web hosting companies like 1and1 where you needed to pay a small amount per month and you would have a web site; however, the question was, "will it scale?". Being on a platform like Heroku, Windows Azure, PHPFog gives you the options you need to scale accordingly based on your social application's virality. We all know how it feels when you launch and your site goes down with the increase traffic. 

Below is a snippet of my shell that I used to get up and running within a matter of seconds. This workflow assumes you already have the Heroku Toolbelt or Gem installed (gem install heroku).


Let's walk through what I did!

  1. Created a heroku application and named it "hello-php-jbueza"
  2. Initialized the current folder as a git repository (git init)
  3. Create a file "index.php" with phpinfo(); 
  4. Added the file and committed changes to my local repository
  5. Pushed to heroku remote (master)
Hope that helps! I understand there are other great platforms to deploy to like PHPFog and Windows Azure, but if you're using Heroku at your next hackathon (and you want to use PHP), this should get you up and running quickly.

Cheers!
Jaime
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!