Fix: prevent environment hijacking/crash in multi-site setups#2175
Fix: prevent environment hijacking/crash in multi-site setups#2175Dana-Johnson wants to merge 1 commit into
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
The Issue:
In multi-site environments, the CLI's
checkEnvironmentshortcut can globally hijack the process environment. If one registered site is missing aconfig.production.jsonwhile others are running, the CLI may attempt to force a global development mode, leading to crashes or state pollution.The Fix:
Modified
checkEnvironmentinlib/instance.jsto only allow the automatic development-mode fallback if the CLI is managing a single instance. In multi-site configurations, the CLI now bypasses this shortcut, maintaining environment stability across the stack.