Ok, so this trilogy wasn’t supposed to have a part 4. In Getting going with Heroku and PHP (part 1), part 2 and part 3, I detailed how I got my website successfully published using Git to push to my “master” branch, have Heroku set to automatically deploy from this branch, and have my Procfile set to point…

In Getting going with Heroku and PHP (part 1) and part 2 I detailed how I made Heroku happy to build and deploy my website, but was now getting Server 5o3 errors when trying to view it in the browser.  Not a good place to be! I then (slowly, too slowly) figured out it was because of the…

In Getting going with Heroku and PHP (part 1) I detailed how I start using “git subtree” to push my “build” folder into a separate repo, which Heroku would then automatically deploy. However, Heroku wasn’t happy that it was having to make so many assumptions, so my next step was to try and be more explicit. My…

As a preface, I’ve tinkered a little bit with Heroku and Ruby, so I already had the Heroku client installed, but it’s not something that I’d worked with properly.  However, I had a little project I wanted to work on, and it seemed like a good idea to have a play, so here’s how it went.…