Add E2E_DATABASE_URL env

[pepeladeira]

Summary by CodeRabbit

• Documentation
  • Updated local development setup guide with additional environment variable configuration details for E2E testing setup.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update adding a new E2E_DATABASE_URL environment variable example to the local development guide, with a MySQL connection string reference in two locations.

Changes

Cohort / File(s)	Summary
Documentation Updates local-development.mdx	Added E2E_DATABASE_URL environment variable entry with MySQL connection string example in the E2E environment variables section and the Add E2E API token workflow steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A database URL, so neat and divine,
Local development flows like fine wine,
MySQL connection strings dancing in place,
Documentation gleams with environment grace! 🌿

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding the E2E_DATABASE_URL environment variable to documentation. It is concise and specific about the primary modification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

local-development.mdx (1)

544-544: Consider using a separate database for E2E tests.

The E2E_DATABASE_URL points to the same database as DATABASE_URL (line 294). While this simplifies local setup, E2E tests typically benefit from an isolated database to prevent test data from interfering with development data and to ensure clean test runs.

Consider using a separate database name, such as:

E2E_DATABASE_URL="mysql://root:`@localhost`:3306/planetscale_e2e"

This would require creating the additional database in the Docker setup, but provides better isolation between development and testing environments.

---

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.}