Update Nimbus README with enw allowedHosts setup

[Oksamies]

No description provided.

[coderabbitai]

Walkthrough

The README in apps/cyberstorm-remix was updated to replace instructions for editing vite.config.ts with guidance to configure local test domains via the environment variable __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS (e.g., __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS=.thunderstore.temp). It notes that localhost remains enabled by default. No exported or public APIs were changed.

Possibly related PRs

• Update cyberstorm-remix Readme with up-to-date setup guide #1530: Also modifies the cyberstorm-remix README’s local dev instructions regarding adding .thunderstore.temp to Vite allowed hosts.
• Dynamically resolve allowedHosts for local dev envs #1557: Changes vite.config.ts to dynamically resolve Vite allowedHosts (including .thunderstore.temp), relating to the same configuration area.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	No pull request description was provided, so there is no contextual information about the changes beyond the title and file diffs. This absence means the description fails to convey any details of the update.	Please add a brief description summarizing the README update for using the VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS environment variable instead of editing allowedHosts directly.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title accurately summarizes the primary change by indicating an update to the Nimbus README for setting up allowedHosts, which aligns with the modifications described in the summary. It is concise and focuses on the main change without extraneous details.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 10-06-update_nimbus_readme_with_enw_allowedhosts_setup

---

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

[Oksamies]

• Update Nimbus README with enw allowedHosts setup #1568 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/cyberstorm-remix/README.md (1)

39-40: Tighten the wording in step 5.

Change “in to” → “into” for smoother reading.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8a8c170 and 9654c57.

📒 Files selected for processing (1)

• apps/cyberstorm-remix/README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build
• GitHub Check: Generate visual diffs

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 10.70%. Comparing base (37e7161) to head (9654c57).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1568   +/-   ##
=======================================
  Coverage   10.70%   10.70%           
=======================================
  Files         285      285           
  Lines       19871    19871           
  Branches      385      385           
=======================================
  Hits         2128     2128           
  Misses      17743    17743           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[anttimaki]

Should this just be part of step 4? "Here's a example of file contents for development environment:"

[Oksamies]

Wanted to keep it as a separate step to pronounce the thought process of "what is the local domain I'll be using". I can change it if my thinking sounds weird