Change rails server with test environment

[me3eh]

If there is a reason why it should be running in development mode, just let me know :D with RAILS_ENV=test it will just run with test database

Summary by CodeRabbit

• Documentation
  • Removed outdated local test database setup guidance.
  • Added instructions for enabling live-reload in the test environment to improve iterative testing.
  • Noted an optional port override when the default port is in use.
  • Clarified the recommended command to start the server in the test environment for running end-to-end tests.
  • Retained existing warnings about running on certain hosts/configurations.

[coderabbitai]

Walkthrough

Removed local database.yml Cypress guidance from README.md; added live-reload instructions for test.rb using ENV['CYPRESS'], noted optional port override, and updated the Rails server startup command to run under the test environment with CYPRESS=1 RAILS_ENV=test bin/rails server -p 5017.

Changes

Cohort / File(s)

Change Summary

Documentation — README update README.md

Removed guidance for modifying database.yml for local Cypress testing and deleted YAML examples; added live-reload configuration snippet for test.rb using config.enable_reloading = ENV['CYPRESS'].present? and config.action_controller.allow_forgery_protection = ENV['CYPRESS'].present?; noted optional port override and updated Rails server startup command to CYPRESS=1 RAILS_ENV=test bin/rails server -p 5017.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I'm a rabbit, nose twitching in the light,
I hopped through the README and tidied the night.
YAML whispers gone, live reload takes flight,
Tests now start true on a dedicated port bright. 🐇

---

📜 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 efdac13 and 1026c5e.

📒 Files selected for processing (1)

• README.md (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests

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

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[grantspeelman]

the test environment is usually not setup for reloading, so you would also need to add to the README to update the test.rb and enable reloading if CYPRESS env is set.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

137-138: Explicit Environment Specification for Rails Server
The updated command now includes RAILS_ENV=test, which makes it clear that the server will run using the test database. This change meets the PR objective well. However, please consider adding a brief note or reference in the documentation pointing out that some development conveniences (like code reloading) might be disabled by default in the test environment unless explicitly enabled as shown above.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5956f5f and efdac13.

📒 Files selected for processing (1)

• README.md (2 hunks)

🔇 Additional comments (1)

README.md (1)

120-124: Live Reload Configuration Update
The new section clearly instructs users to update the test.rb file by setting config.enable_reloading = ENV['CYPRESS'].present?. This aligns with the feedback suggesting that live reloading be enabled conditionally when running the Rails server in the test environment. Please ensure that users understand this change as they might need to tweak their test configuration further if reloading behaves unexpectedly.