01 March 2014

When we first started engaging with Pantheon, it became clear we would need a true Drupal distribution. We had simply created a codebase and pushed a pre-configured database a tarball codebase. That wasn’t going to cut it. So I started on my journey to add to the install profile everything needed to get a fully-formed Apigee portal up and going. Pantheon’s Instructions where helpful but it took a lot of trial and error. I must have installed from scratch the portal at least 1000 times. That’s not an exaggeration.

Some of the things you don’t realize at the outset:

  • Complex tasks need to be split up into smaller tasks and submitted to the installer as a batch array so they don’t time out the installer. Just because it works on your local version doesn’t mean it’s going to work in a pantheon hosting environment. They have throttled CPUs and limited resources. You have to take this into an account.

  • In the module install batch, Modules will install in alpha order, no matter how you add them to the array. And they don’t always install their dependencies. It behooves you to iterate thru their dependencies and add them to the array of modules to install.

more as I think of them.