chore: change paths

[coodos]

Description of change

Fix bad paths

Issue Number

Type of change

• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Chores
  • Updated environment variable file path references across multiple platform services and configurations to reflect changes in the codebase directory structure.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This pull request updates environment variable loading paths across 38 files in a monorepo by incrementing the relative directory depth for .env file resolution. All changes follow the same pattern: adjusting dotenv.config() or envDir paths to point one level higher in the directory hierarchy, reflecting a monorepo structure reorganization.

Changes

Cohort / File(s)	Summary
Database Data Source Configuration platforms/blabsy/api/src/controllers/WebhookController.ts, platforms/cerberus/client/src/database/data-source.ts, platforms/dreamsync/api/src/database/data-source.ts, platforms/ecurrency/api/src/database/data-source.ts, platforms/emover/api/src/database/data-source.ts, platforms/ereputation/api/src/database/data-source.ts, platforms/esigner/api/src/database/data-source.ts, platforms/evoting/api/src/database/data-source.ts, platforms/file-manager/api/src/database/data-source.ts, platforms/group-charter-manager/api/src/database/data-source.ts, platforms/pictique/api/src/database/data-source.ts, platforms/profile-editor/api/src/database/data-source.ts	Updated dotenv.config() paths to resolve .env files one directory level higher, affecting environment variable loading for database connections and TypeORM configuration.
API Entry Points platforms/blabsy/api/src/index.ts, platforms/dreamsync/api/src/index.ts, platforms/ecurrency/api/src/index.ts, platforms/emover/api/src/index.ts, platforms/ereputation/api/src/index.ts, platforms/esigner/api/src/index.ts, platforms/file-manager/api/src/index.ts, platforms/pictique/api/src/index.ts	Updated dotenv.config() paths in main application entry points to load .env files from a parent directory level.
Web3 Adapter Watchers platforms/blabsy/api/src/web3adapter/watchers/firestoreWatcher.ts, platforms/cerberus/client/src/web3adapter/watchers/subscriber.ts, platforms/dreamsync/api/src/web3adapter/watchers/subscriber.ts, platforms/ecurrency/api/src/web3adapter/watchers/subscriber.ts, platforms/ereputation/api/src/web3adapter/watchers/subscriber.ts, platforms/esigner/api/src/web3adapter/watchers/subscriber.ts, platforms/evoting/api/src/web3adapter/watchers/subscriber.ts, platforms/file-manager/api/src/web3adapter/watchers/subscriber.ts, platforms/group-charter-manager/api/src/web3adapter/watchers/subscriber.ts, platforms/pictique/api/src/web3adapter/watchers/subscriber.ts, platforms/profile-editor/api/src/web3adapter/watchers/subscriber.ts	Updated .env file path resolution in web3 subscriber modules, adjusting relative directory traversal depth for environment configuration loading.
Client Configuration Files platforms/calendar/client/next.config.ts, platforms/dreamsync/client/vite.config.ts, platforms/ereputation/client/vite.config.ts	Updated envDir or helper function paths to resolve environment files from a parent directory in Next.js and Vite configurations.
Scripts and Database Utilities platforms/dreamsync/api/scripts/migrate-summaries.ts, platforms/dreamsync/api/test-matchmaking-mock.ts, platforms/ecurrency/api/src/scripts/backfill-accounts.ts, platforms/ereputation/api/src/database/seed.ts	Updated dotenv.config() paths in utility scripts and database seeders to reference .env files from a higher directory level.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~8 minutes

This is a homogeneous, repetitive change applied consistently across 38 files with identical patterns—simple relative path adjustments for environment file resolution. No logic, control flow, or exported APIs were altered; all changes are cosmetic path updates requiring verification of correct directory depth alignment.

Suggested reviewers

• sosweetham
• ananyayaya129
• Bekiboo

Poem

🐰 A tale of paths, both new and old,
Dotfiles climbing, brave and bold,
Up one level, across the land,
Config files now understand,
The monorepo's gentle hand! 🌱

🚥 Pre-merge checks | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is largely incomplete despite following the template structure. Critical sections lack detail: no issue number provided, testing approach is blank, all checklist items are unchecked, and 'Fix bad paths' provides no context.	Complete the description by adding issue number reference, explaining how changes were tested, checking off completed items, and providing specific details about what paths were fixed and why.
Docstring Coverage	⚠️ Warning	Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'chore: change paths' is vague and generic, using non-descriptive terms that don't clearly convey what paths are being changed or why.	Provide a more specific title that describes the actual change, such as 'chore: update environment file paths in platform configurations' or similar descriptive phrasing.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/env-paths

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}