rerun --connect works

Author: emilk

crates/top/re_sdk/src/recording_stream.rs

@@ -409,7 +409,7 @@ impl RecordingStreamBuilder {
     /// locally hosted gRPC server.
     ///
     /// The server is hosted on the default IP and port, and may be connected to by any SDK or Viewer
-    /// at `rerun+http://127.0.0.1:9876/proxy`.
+    /// at `rerun+http://127.0.0.1:9876/proxy` or by just running `rerun --connect`.
     ///
     /// To configure the gRPC server's IP and port, use [`Self::serve_grpc_opts`] instead.
     ///
@@ -1910,6 +1910,8 @@ impl RecordingStream {
     ///
     /// To configure the gRPC server's IP and port, use [`Self::serve_grpc_opts`] instead.
     ///
+    /// You can connect a viewer to it with `rerun --connect`.
+    ///
     /// The gRPC server will buffer all log data in memory so that late connecting viewers will get all the data.
     /// You can limit the amount of data buffered by the gRPC server with the `server_memory_limit` argument.
     /// Once reached, the earliest logged data will be dropped. Static data is never dropped.

docs/content/reference/sdk/operating-modes.md

@@ -48,7 +48,7 @@ You will need to start a stand-alone Viewer first by typing `rerun` in your term
 
 ### `serve_grpc`
 Calling `serve_grpc` will start a Rerun gRPC server in your process, and stream logged data to it.
-This gRPC server can then be connected to from the Rerun Viewer, e.g. by running `rerun --connect localhost/proxy`.
+This gRPC server can then be connected to from the Rerun Viewer, e.g. by running `rerun --connect`.
 The gRPC server acts as a proxy, buffering and forwarding log data to the Rerun Viewer.
 
 You can also connect to the gRPC server from a Rerun Web Viewer.