ReferenceAsk
A

Realtime

Inspect and exercise the app's realtime events from the terminal: list active channels, publish a test event, and tail publishes live.
remy-admin events

The observability side of app events. When a realtime feature is not behaving, these commands answer the two questions that matter: is the backend publishing what I think it is, and is anyone subscribed to the channel I think they are. events channels list shows the channels with recent activity and their live subscriber counts, which is usually enough to catch the most common bug on its own: a channel with subscribers but no publishes, or the reverse, means the frontend and backend are spelling the channel differently. events publish sends a real event through the same path the app uses, so you can verify a frontend subscriber before the backend trigger even exists. events tail prints publishes as they happen.

Every command takes a scope, because publishes and subscriptions never cross worlds: live by default, or a specific preview or development session. A tunnel session's events are visible only under its own development scope, which is what lets you watch a feature you are actively building without touching production traffic.

3 entries