[#20] include project config, Mailpit setup

[joshuapease]

Overview

• Inclue craft project config in starter project #20

I think we could unlock some cool super-powers by committing baseline project config YAML in our starter.

• Running ddev craft install will also auto-install all of the plugins (instead of that being a separate step after installing Craft.
• We can pre-configure mail to use STMP and route all messages through mailpit locally (prevents accidental emails to users)
  • Included in this PR
• We can configure default Volumes and S3 configs.
  • Asset and S3 configuration #15
• We can include a starter page builder and blocks rather than rely on a plugin to import/export JSON versions of blocks.
  • Add a set of starter page builder blocks #26

What this PR does

• Include the default project config generated when running craft install
• Configures mail settings to use SMTP and Mailpit for local development
• Updates composer-scripts/post-create-project.php to replace any "starter" related text with the project specific text that the user is prompted with.

Testing steps

# Make an empty directory for the starter project
mkdir test-craft-starter

cd test-craft-starter

# composer create-project
docker run --rm -it -v "$PWD":/app -v ${COMPOSER_HOME:-$HOME/.composer}:/tmp composer create-project viget/craft-site-starter=dev-jp/20-include-project-config ./ --ignore-platform-reqs

# After the project has been scaffolded

ddev craft/install

ddev launch

[joshuapease]

Hard coding these values into the DDEV config makes it harder to accidentally override these with production credentials.

[joshuapease]

This is relatively simple to Regex replace everything within the tags

[joshuapease]

Realized I could use these Craft helpers, which makes ScriptHelpers super minimal (only need it for file text replacements).

[joshuapease]

This assumes we'll use some kind of SMTP service on our projects.

I've found it to be necessary to get password reset emails to work, even for small clients.

It's super affordable: https://aws.amazon.com/ses/pricing/

[joshuapease]

We remove these licenseKey lines. They auto-regenerate with new numbers when you create a new project and visit the Craft admin for the first time.

[joshuapease]

It feels a little funny that these UUIDs will be repeated across projects... but it would be impossible for two Craft projects to be installed using the exact same DB tables, so it's not really an issue.