jasonlttl / wanderus Goto Github PK

In this file

.circle/scripts/02-init-site-under-test-clone-existing.sh

We are doing a config import using a cloned version of the test database. This results in uuid conflicts. The top of the script says...

# Use EITHER this script OR the re-install-new script; do not run both.

Possible ways to fix this wouldbe to switch to the re-install-new OR reinstall test/prod now that we have a config based workflow.

Not super sure which is preferred. Installer would appear to be a way to test a distribution and clone more an existing site and possibly migrations. Do I even want tests running with prod data?

This project allows you to load configuration as if it were an install profile. This seems to be more what we want than an actual install profile.

https://www.drupal.org/project/config_installer

This should start off as a fork of standard and then we can customize it.

Create a simple content type with few fields.

Drupal's default mode of prefixing all fields is not generally necessary and creates rather painful code. Turn it off.

Create a couple of scripts to quickly launch a primitive local development environment with sqlite and php's server.