• Combine the main .env.example file with any .env.example
  files from custom plugins during setup
• Also support ignoring commented-out lines in .env.example files
• Also ignore blank lines
• also format with shfmt
• also fix one shellcheck lint error

Impact: minor
Type: feature

Issue

Sometimes reaction custom plugins need environment variable settings, and need to provide examples. Previously only the main reaction .env.example file was used to initially populate the user's .env file. Any settings from custom plugins would require a documented manual process to initially setup.

Solution

Search the imports/plugins/custom directory for any files named .env.example and incorporate those into the main .env.

Breaking changes

The script has always avoided overwriting any values that already exist in the file, and that behavior is retained.

Testing

I locally tested a few scenarios

• no extra .env.example files
• several custom plugins with .env.example files
• a custom plugin with an .env.examplein a docs subdire

How to test this yourself

• check out this feature branch
• put a bunch of varying .env.example files in your directory tree including the reaction project directory and anywhere under imports/plugins/custom
• Populate those files with a mix of KEY=value vars and commented out lines
• Run bin/setup
• Examine your project root .env file and make sure it has the values you expect