geerlingguy / drupalvm-live Goto Github PK

Right now, I have Drupal configured to use a page cache expiry of 15 minutes. But Varnish should be easy enough to configure via the geerlingguy.varnish role that Drupal VM provides so we can use cache tags and have immediate cache invalidation for any content changes.

Basically, people should feel comfortable enough committing a Vault-encrypted file—as long as the password they used to encrypt it is a secure password (e.g. lots of entropy).

If you use a password like testtesttest to encrypt an Ansible Vault-encrypted file, then someone could grab the public repo and easily brute force the password (since there's no other protection mechanism, and anyone can have Ansible Vault installed).

Anyways, I don't know if I want to do anything more here... but it would at least be good to add a stern warning about knowing what you're doing before you post anything secret to the wider world—even if it's encrypted!

See Drupal VM docs: http://docs.drupalvm.com/en/latest/extras/selenium/

And see BLT for more practical examples, too.

TODO.

As the title says... after finishing #7, it would be nice to maybe even get Drupal VM to build inside Travis CI, then run the Behat tests. That would allow Drupal VM to basically be the end-to-end build tool, and also make it so that CI tests are run in exactly the same environment as local and prod!

In order to prevent having to type that env var out every time running vagrant up or vagrant provision (otherwise Ansible won't be able to decrypt the secrets.yml file), that should be added to the project's delegating Vagrantfile.

As the title says... see Setting up Faceted Apache Solr search in Drupal 8.