feat(rw-backend): periodic site reload#40
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
yumike
force-pushed
the
feat/periodic-site-reload
branch
from
29efb56 to
dddcdf2
Compare
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
1 participant
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.
Summary
RwSiteinstances now periodically check S3 for upstream changes and reload only when content has changed (using@rwdocs/core0.1.21's conditionalreload())rw.processingIntervalconfig (BackstageHumanDurationformat, same pattern ascatalog.processingInterval) — no reload if omittedResolves the need to restart Backstage when new docs are uploaded to S3.
Related: rwdocs/rw#257
Test plan
Hub.reloadAll()— verifies per-site reload, skip-if-unchanged logging, and error resilienceprocessingInterval, upload new docs to S3, verify reload without restart🤖 Generated with Claude Code