Fix Rotator usability + local-only safety (addresses setup confusion)#446
Open
Delerius wants to merge 2 commits intoaccius:mainfrom
Open
Fix Rotator usability + local-only safety (addresses setup confusion)#446Delerius wants to merge 2 commits intoaccius:mainfrom
Delerius wants to merge 2 commits intoaccius:mainfrom
Conversation
This update stabilizes the Rotator and N3FJP integrations and improves local-only UX clarity. Rotator: - Explicitly treated as a local-only feature - Hidden/disabled in hosted deployments - Added Integrations → Local-only setup section - Added quick start instructions - Prevented runtime errors when backend is unavailable - Ensured overlay state does not auto-enable unexpectedly N3FJP: - Cleaned up on-map controls (moved configuration to Integrations) - Added display window options up to 24 hours - Added server retention configuration support via .env - Auto-enable map layer when integration is enabled - Added warning if layer is disabled - Fixed rendering crash in display window selector Server: - Support for N3FJP_QSO_RETENTION_MINUTES in .env and .env.example This ensures hosted OHC never crashes, while local installations gain full functionality with clear setup guidance.
Open
Contributor
|
Is there a way to disable it when running locally? I'm working on some unrelated stuff and need to turn on debug logging. The rotator stuff is really chatty. Strike that, looks like it was addressed in that batch of 70 of commits a few hours ago. |
Contributor
Author
|
Note: PR #426 added a basic hosted safety gate for Rotator (local-only panel list + endpointUrl). This PR builds on that by adding explicit Local-only Integrations UX, documentation, and graceful behavior when backends are unavailable |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses usability and stability concerns around the Rotator feature.
The original issue was that Rotator was merged but:
What this update does:
Rotator:
N3FJP:
Hosted behavior:
Local behavior:
This should resolve the previous confusion about how Rotator is intended to work and ensure safe operation in both hosted and local environments.