feat: run database migrations automatically on server start

[UlisesGascon]

closes #231

Summary by CodeRabbit

• Chores
  • The application now automatically applies the latest database migrations before starting the server, ensuring the database schema is always up to date.
  • Simplified the test environment setup by adjusting the server start command used in automated tests.

[coderabbitai]

"""

Walkthrough

A new npm lifecycle script "prestart" was added to the package.json scripts section to run "npm run db:migrate" automatically before the existing "start" script ("node server.js") executes. This ensures database migrations are applied prior to server startup without modifying the "start" script itself. Additionally, the explicit setting of NODE_ENV=test was removed from the Playwright test configuration's local server start command, simplifying it to npm run start.

Changes

File(s)	Change Summary
package.json	Added a "prestart" script to run database migrations before the "start" script executes.
playwright.config.js	Removed explicit NODE_ENV=test from the local server start command in Playwright config.

Assessment against linked issues

Objective (Issue #)	Addressed	Explanation
Always run the migrations when starting the server (#231)	✅

Poem

The server hops, the schema's right,
Migrations run before first byte.
No tables lost, no columns stray,
All up to date—hip hip hooray!
With every start, the code's in line,
A happy bunny—by design! 🐇✨
"""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 24381fc and eb26bef.

📒 Files selected for processing (2)

• package.json (1 hunks)
• playwright.config.js (1 hunks)

🔇 Additional comments (1)

package.json (1)

22-22: Great implementation of automatic migrations!

Adding a prestart script is a clean way to ensure migrations run automatically before the server starts. This approach follows npm's lifecycle convention and maintains separation of concerns.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[UlisesGascon]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.