Repository navigation
Stabilize gallery live updates and support native celld fleets - #47
Merged
Merged
Conversation
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
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.
ATM's HTTP-mode Classic ELB rejects the gallery WebSocket upgrade. The client refreshed on failed reconnects, remounted the empty library, and moved content when connection status changed. Native Worker apps were also unavailable because the existing celld provider supported a single host rather than ATM's bucket-backed fleet.
Use an authenticated HTTP event stream for hosted live updates, reconcile missed changes without clearing the loaded view or dirty editors, and keep connection/copy feedback in stable layout slots. Refine onboarding, Secrets, request and schedule forms within the existing gallery UI.
Add a
celld-fleetprovider with one authenticated publisher for app and host updates. It preserves Artifacts as the default Worker, app-owned native resources, and the deployment registry in the fleet bucket. Native service bindings carry requests; app cron handlers run in their own environments. Publication checks adoption on all nodes and retains reconciliation state after interruption. Build and publish matching runtime and publisher Docker targets.Validated locally:
Production is unchanged. The separate ATM manifests PR must use matching published images from the merged source commit before rollout. Public app WebSockets still require an ingress that supports upgrades.