Rename 'bun up' to 'bun db'

[yamcodes]

Description

Update the "bun up" command to "bun db" since it's used to spin up a db container. It's a better name. If we use "bun docs" to spin up a docs server, we should use "bun db" to spin up a db server.

---

PR Checklist

• Read the Developer's Guide in CONTRIBUTING.md
• Use a concise title to represent the changes introduced in this PR
• Provide a detailed description of the changes introduced in this PR, and, if necessary, some screenshots
• Reference an issue or discussion where the feature or changes have been previously discussed
• Add a failing test that passes with the changes introduced in this PR, or explain why it's not feasible
• Add documentation for the feature or changes introduced in this PR to the docs; you can run them with bun docs

Summary by CodeRabbit

• Documentation
  • Updated setup instructions to now use the bun db command for initiating the database service, replacing the previous bun up command in both the quickstart and getting-started guides.
• Chores
  • Adjusted the underlying command reference in the configuration to align with the new bun db command.
• Bug Fixes
  • Removed the app service configuration from the Docker Compose setup.

[coderabbitai]

Walkthrough

This pull request updates the command used to spin up the Postgres+Bun container. The command is changed from bun up to bun db in the Quickstart section of the README, in the getting-started documentation, and within the package.json scripts. Additionally, the app service configuration has been completely removed from the docker-compose.yml file. The underlying functionality remains unchanged; only the command names and service definitions have been updated.

Changes

File(s)	Summary
README.md, docs/getting-started.md	Updated the command from bun up to bun db in documentation instructions.
package.json	Renamed the script command key from "up" to "db" while referencing the same shell script.
docker-compose.yml	Removed the app service configuration entirely from the Docker Compose setup.

Poem

I'm a rabbit in the code, hopping with glee,
Updated commands now set us free.
From "up" to "db", a change so clear,
In docs and scripts, the message is here.
May every commit bring joy anew,
For I rejoice in changes, just like you!

---

📜 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 5e89422 and a385091.

📒 Files selected for processing (1)

• docker-compose.yml (0 hunks)

💤 Files with no reviewable changes (1)

• docker-compose.yml

---

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

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

[Hajbo]

What do you think about removing the app service from the docker-compose file? I think that is only for devcontainers, but we don't really use it.