Update Nimbus README with enw allowedHosts setup

[Oksamies]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@Oksamies has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 52 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5ad01db and 56e9f94.

📒 Files selected for processing (1)

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

Walkthrough

The apps/cyberstorm-remix README was updated: instead of instructing to uncomment a host in vite.config.ts, it now instructs setting local test domains via the environment variable __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS (e.g., __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS=.thunderstore.temp). 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 updates the cyberstorm-remix README’s local dev instructions for 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), touching the same configuration area.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The description is missing entirely and provides no context about the README update, making it impossible to determine its relevance to the changeset.	Please add a brief description summarizing the changes to the README, specifically the new environment variable–based allowedHosts setup.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title accurately reflects the primary change of updating the Nimbus README to include the allowedHosts setup instructions, though it contains a minor typographical error.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

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 9.89%. Comparing base (ed81119) to head (56e9f94).

Additional details and impacted files

@@          Coverage Diff           @@
##           master   #1568   +/-   ##
======================================
  Coverage    9.89%   9.89%           
======================================
  Files         308     308           
  Lines       22497   22497           
  Branches      404     404           
======================================
  Hits         2225    2225           
  Misses      20272   20272           

☔ 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

[anttimaki]

I'm not exactly sure I understand what you mean by that? Doesn't the "Setup nginx proxy" phase and step 4 above pretty much tell the user to use thunderstore.temp as the local domain? Using something else just... doesn't work, the way all the pieces are currently set up?

I also noticed the main/root README sort of contradicts what's said in this README. The main README should perhaps be updated to link to this README rather than try to repeat the information there? Doesn't need to be part of this PR.

[Oksamies]

Updated the changes to your suggestions