Hello all. I’ve searched the Pantheon docs and power-users channel, but I could not find any info re: how to best install and run CiviCRM (https://civicrm.org) on a Drupal 8 site (standard profile with non-composer based workflow). I know I can install a Drupal 7.65 + CiviCRM (currently 5.10.3) site using the CiviCRM Starter Kit (https://pantheon.io/docs/start-state/). However, based on my experience installing a new site using the CiviCRM Starter Kit is one thing, but getting it to run smoothly on Pantheon is a whole different beast so I assumed the same would be true for a Drupal 8 site (if not more so). IMHO, if it were “easier” to run a Drupal 8 + CiviCRM site on the Pantheon Platform (or if there was at least a doc page with detailed instructions) then I think it would be a game changer for many non-profits. In the meantime, any pointers or a push in the right direction with any required patches would be much very appreciated!
The starterkit is working smoother now, after ironing out some Pantheon-specific issues.
@chrismatthews if you’re going to attempt Drupal 8 + CiviCRM, I recommend you point templates_c to /tmp which makes it run much more smoothly. But this requires a patch to ensure the rest of the files can be saved in the regular files. There are a couple other small patches that probably also apply for Drupal 8.
I recommend you point templates_c to /tmp which makes it run much more smoothly. But this requires a patch to ensure the rest of the files can be saved in the regular files.
Can you post that patch here?
There are a couple other small patches that probably also apply for Drupal 8.
Can you post those patches here?
My goal is to get a comprehensive list of installation best practices and necessary patches so that anyone using Drupal 8 + CiviCRM on Pantheon knows exactly how to get up and running smoothly. Ideally, I would like to add this information to the official Pantheon docs so that others can contribute and keep the the doc up-to-date.
@chrismatthews there’s a full list of patches here https://github.com/herbdool/civicrm-starterkit-drops-7/blob/master/profiles/civicrm_starterkit/civicrm_starterkit.make. Not all of them are applicable. For instance, some are required so CiviCRM can be installed in a profile and if you don’t have a custom upstream that’s not a concern.
These two are important:
These patches do a few things. CiviCRM assumes we have access to configure the Nginx config which we don’t. So it allows setting a private file path and a public file path. And it removes setting the public file path based on the templates_c path. This particular patch isn’t up to par to be accepted into core, since they want it to be done in a different way, but it works just fine.
The first listed patch are suggested changes to civicrm.settings.php file. It includes configuring cache to use Redis, setting file paths, and using Pantheon environmental variables for dbs, file paths, etc. You can adapt as needed.
It was created by the previous maintainer of the starterkit and seems to be required, but I don’t know why we need it.
@herb, thank you very much! I will work on testing and then writing up a doc page for Pantheon docs.