Skip to content

Commit f667ca1

Browse files
committed
Update docs
1 parent e2ef6f1 commit f667ca1

File tree

1 file changed

+15
-3
lines changed

1 file changed

+15
-3
lines changed

docs-src/index.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
InEngine.NET allows commands to be queued, scheduled, and run directly.
1+
InEngine.NET allows commands to be [queued](queuing), [scheduled](scheduling), and run directly.
22

33
## How does it work?
44

@@ -32,6 +32,18 @@ Now run a command in a container:
3232
docker run --rm inengine -pInEngine.Core echo --text"Hello, world"
3333
```
3434

35-
You can get started with either the
36-
Get started by reading up on [commands](commands), then [scheduling](scheduling) and [queuing](queuing).
35+
Want to queue our example echo command to run in (possibly) another server?
3736

37+
Use the core plugin's **queue:publish** command:
38+
39+
```bash
40+
inengine.exe -pInEngine.Core queue:publish --command-plugin=InEngine.Core.dll --command-verb=echo --args "text=Hello, world"
41+
```
42+
43+
How do we consume that queued echo command?
44+
45+
Use the core plugin's **queue:consume** command of course:
46+
47+
```bash
48+
inengine.exe -pInEngine.Core queue:consume
49+
```

0 commit comments

Comments
 (0)