Move .env.example to the .defaults folder

[CLHatch]

Pull request

Purpose
Describe the problem or feature in addition to a link to the issues.

Approach
How does this change address the problem?

Open Questions and Pre-Merge TODOs
Check all boxes as they are completed

• Use github checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage
Links to blog posts, patterns, libraries or addons used to solve this problem

Requirements
Check all boxes as they are completed

• These changes meet the standards for contributing.
• I have read the code of conduct.

Summary by Sourcery

Enhancements:

• Align the COMPOSE_ENV default example file location with the central .defaults folder for consistency across configuration defaults.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the default docker-compose environment file path to use the shared .defaults folder instead of a script-local .env.example, centralizing default configuration handling.

File-Level Changes

Change	Details	Files
Point the COMPOSE_ENV_DEFAULT_FILE variable to the shared defaults directory rather than a script-local .env.example file.	Change COMPOSE_ENV_DEFAULT_FILE to reference DEFAULTS_FOLDER for the .env.example location Ensure the default compose env file path is consistent with other default configuration paths	.includes/global_variables.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since COMPOSE_ENV_DEFAULT_FILE now relies on DEFAULTS_FOLDER, double-check that all other references to .env.example in the scripts are updated to use this variable or the new location to avoid path mismatches.
• Confirm that any logic or tooling that previously assumed .env.example lived under ${SCRIPTPATH} (e.g., manual commands, helper scripts) has been updated or will still behave correctly with the new ${DEFAULTS_FOLDER} path.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since `COMPOSE_ENV_DEFAULT_FILE` now relies on `DEFAULTS_FOLDER`, double-check that all other references to `.env.example` in the scripts are updated to use this variable or the new location to avoid path mismatches.
- Confirm that any logic or tooling that previously assumed `.env.example` lived under `${SCRIPTPATH}` (e.g., manual commands, helper scripts) has been updated or will still behave correctly with the new `${DEFAULTS_FOLDER}` path.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}