Build initial Drupal 8 codebase if not present

[geerlingguy]

So, right now the Kubernetes branch is using the drupal repository, which includes a copy of the Drupal codebase, but is not specifically intended for production usage (though it could be hacked around to do so...).

One annoying side effect is that on every reboot or Pod replacement of the drupal8 service, we end up with a codebase divorced from the database!

So, instead, I'd like to:

• See if a Drupal container image has been built already.
• Build one if not (or use a decent one off Docker Hub... Wodby maybe?)
• See if we have an existing Drupal codebase.
• If not, build a Drupal codebase using Drupal Project.
• See if we have an existing Drupal installation.
• If not, install Drupal.

For all of these steps, they should happen after Kubernetes is started and stabilized.

I haven't yet decided if I want to just host a separate Git repo with the Drupal codebase in it on GitHub, so I don't have to rebuild it forever and ever for testing purposes... it's kind of annoying and takes a bit of time. But it might be better for educational purposes anyways :/

[geerlingguy]

New docker image for building off of: https://hub.docker.com/r/geerlingguy/drupal/

[geerlingguy]

Opened #108 as a likely prerequisite.

Also doing a bit more (quicker) testing in #107. Easier than reprovisioning all the Pis each time :)

[geerlingguy]

D'oh, I could just recommend people set the environment vars in settings.php instead, e.g.:

How to Use Environment Variables for your Drupal Settings with Docksal. Code example:

$databases['default']['default'] = [
  'driver' => 'mysql',
  'database' => getenv('DRUPAL_DATABASE'),
  'username' => getenv('DRUPAL_DATABASE_USER'),
  'password' => getenv('DRUPAL_DATABASE_PASSWORD'),
  'host' => getenv('DRUPAL_DATABASE_HOST'),
];

[geerlingguy]

As part of geerlingguy/drupal-container#3, I'm adding a 'download Drupal core if it's not already present' feature to the entrypoint.

[geerlingguy]

Blocked by two things:

1. Create an NFS mount for the drupal8 files directory #110 (NFS mount for files directory)
2. settings.php file and permissions for first install... we should really build the codebase in a new container once before setting up the services/deployments.

[geerlingguy]

Worked on #2 above... we'll see if that works.

[geerlingguy]

Was having a 'fun' time debugging why kubectl couldn't do logs on a pod that was running on a separate node from master, and found another place where I need to be more explicit about the IP/interface to listen on for Vagrant-based multi-node architectures.

Posted follow-up comment in kubernetes/kubernetes#60835 (comment) to help if I run into this in the future :)

[geerlingguy]

One good thing... I can confirm that even if you blow away the drupal8 and drupal8-mysql deployments/services entirely, the database is still intact, and you can get right back into things by just bringing the services back up. Nice work, PVs!

[geerlingguy]

Fixed via above commit.