Skip to content

Commit 39a82d9

Browse files
committed
Add option to use --follow-all when running Redis Trigger (to see messages interactively, as apposed to via logs)
Signed-off-by: tpmccallum <tim.mccallum@fermyon.com>
1 parent 9fb4841 commit 39a82d9

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/content/rust-components.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -194,10 +194,17 @@ message on the `messages` channel, the `echo-message` component will be executed
194194
$ redis-server --port 6379
195195
# then, start the Spin application
196196
$ spin up --file spin.toml
197+
# the logs will output the following
197198
INFO spin_redis_engine: Connecting to Redis server at redis://localhost:6379
198199
INFO spin_redis_engine: Subscribed component 0 (echo-message) to channel: messages
199200
```
200201

202+
**Please note**: By default, `stdout` goes only to the logs. This is because Spin is intended to run as a server. If you would like to see the published messages interactively please use the `--follow-all` option, when starting the spin application. For example:
203+
204+
```bash
205+
spin up --file spin.toml --follow-all
206+
```
207+
201208
For every new message on the `messages` channel:
202209

203210
```bash

0 commit comments

Comments
 (0)