How sriail/cloudmoon-inplay works
CloudMoon InPlay is a Cloudflare Worker-hosted browser proxy for CloudMoon’s game and app library. Users open the worker page, sign in to CloudMoon, choose an app, and use the embedded frame and controls; proxy requests are fetched and ad-related content is filtered. The worker also supplies browser-side frame handling and a service-worker cache. The implementation is concentrated in worker.js; unsampled sections limit certainty about internal call wiring, so uncertain links are omitted or marked unverified.
Main entry points: worker.js Main page
Components 16
Worker and proxy
- Worker entry
worker.js - Request routing
worker.js - CloudMoon proxy
worker.js - Response filtering
worker.js - Ad filtering
worker.js
Browser experience
- Main page
worker.js - Game library
worker.js - Layered game frame
worker.js - Frame navigation
worker.js - Player controls
worker.js - Fullscreen handling
worker.js - Client page fixes
worker.js
Offline support
- Service worker
worker.js - Browser cache
worker.js
Other components
- Player
- CloudMoon service
Connections 15
- Player → Worker entry: opens
README.md - Worker entry → Request routing: dispatches
worker.js - Request routing → Main page: serves
worker.js - Player → Game library: selects app
README.md - Main page → Layered game frame: creates
worker.js - Layered game frame → CloudMoon service: loads proxied app
README.md - Main page → Frame navigation: routes links
worker.js - Player → Player controls: uses
README.md - Main page → Client page fixes: injects fixes
worker.js - Player → Fullscreen handling: requests
worker.js - Request routing → CloudMoon proxy: routes proxy requests
worker.js - CloudMoon proxy → CloudMoon service: fetches
worker.js - CloudMoon proxy → Response filtering: processes response
worker.js - Response filtering → Ad filtering: filters markup
worker.js - Service worker → Browser cache: reads and writes
worker.js