Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Template project for deploying WordPress to Heroku
branch: master

This branch is 89 commits behind mhoofman:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
wp-admin
wp-content
wp-includes
.gitignore
.htaccess
README.md
index.php
license.txt
readme.html
wp-activate.php
wp-app.php
wp-atom.php
wp-blog-header.php
wp-comments-post.php
wp-commentsrss2.php
wp-config-sample.php
wp-cron.php
wp-feed.php
wp-links-opml.php
wp-load.php
wp-login.php
wp-mail.php
wp-pass.php
wp-rdf.php
wp-register.php
wp-rss.php
wp-rss2.php
wp-settings.php
wp-signup.php
wp-trackback.php
xmlrpc.php

README.md

WordPress Heroku

This project is a template for getting WordPress up and running on Heroku. It comes with PostgreSQL for WordPress pre-installed in order to use Heroku's existing Postgres backend.

Installation

Clone the repository from Github

$ git clone git://github.com/mhoofman/wordpress-heroku.git

With the Heroku gem, create your app

$ cd wordpress-heroku
$ heroku create --stack cedar
> Creating strange-turtle-1234... done, stack is cedar
> http://strange-turtle-1234.herokuapp.com/ | git@heroku.com:strange-turtle-1234.git
> Git remote heroku added

Add a database to your app

$ heroku addons:add shared-database:5mb
> -----> Adding shared-database:5mb to strange-turtle-1234... done, v3 (free)

Create a new branch for any configuration/setup changes needed

$ git checkout -b production

Copy the wp-config.php

$ cp wp-config-sample.php wp-config.php

Clear .gitignore and commit wp-config.php

$ >.gitignore
$ git add .
$ git commit -m "zomg wordpress"

Deploy to Heroku

$ git push heroku production:master
> -----> Heroku receiving push
> -----> PHP app detected
> -----> Bundling Apache v2.2.19
> -----> Bundling PHP v5.3.6
> -----> Discovering process types
>        Procfile declares types -> (none)
>        Default types for PHP   -> web
> -----> Compiled slug size is 24.9MB
> -----> Launcing... done, v5
>        http://strange-turtle-1234.herokuapp.com deployed to Heroku
>
> To git@heroku:strange-turtle-1234.git
> * [new branch]    production -> master 

After deployment WordPress has a few more steps to setup and thats it!

Usage

  • Because a file cannot be written to Heroku's file system, updating and installing plugins or themes should be done locally and then pushed to Heroku.
  • To run WordPress locally on Mac OS X try MAMP.

Updating

Updating your WordPress version is just a matter of merging the updates into the branch created from the installation.

$ git pull # Get the latest

Using the same branch name from our installation:

$ git checkout production
$ git merge master # Merge latest
$ git push heroku production:master

WordPress needs to update the database. After push, navigate to:

http://your-app-url.herokuapp.com/wp-admin

WordPress will prompt for updating the database. After that you'll be good to go.

Custom Domains

Heroku allows you to add custom domains to your site hosted with them. To add your custom domain, enter in the follow commands.

$ heroku domains:add www.example.com
> Added www.example.com as a custom domain name to myapp.heroku.com

You'll also want to cover the non "www" side of the url.

$ heroku domains:add example.com
> Added example.com as a custom domain name to myapp.heroku.com

Once Heroku recognizes your custom domain(s) you'll then need to setup separate DNS A records for the following ip addresses to point to your domain:

75.101.163.44
75.101.145.87
174.129.212.2

Once the DNS A records propagate, then simply test out your change by hitting the url in the browser to make sure you are good to go. If you are in need of cheap DNS hosting then I would recommend DNSimple.

The last step is updating your WordPress installation to recognize the new domain. You'll need to open up the WordPress Admin Dashboard and go to Settings --> General. From there just update the URL for the WordPress address and you're done.

If you find yourself running into problems, there is a guide posted in the Heroku Docs which can be found here.

Something went wrong with that request. Please try again.