Infrastructure Commands
Manage the Orcher server process.
1
orcher server start [OPTIONS]
2
3
# Examples
4
orcher server start --foreground
5
orcher server start --grpc-port 50051 --http-port 8080
6
orcher server start --database-url postgresql://localhost/orcher
| Option | Default | Description |
|---|
-c, --config | — | Server config file path |
--grpc-port | 50051 | gRPC server port |
--http-port | 8080 | HTTP port: the engine's REST API, health checks and metrics |
--host | 127.0.0.1 | Host address to publish the ports on |
-f, --foreground | false | Run in foreground (not daemonized) |
--database-url | env DATABASE_URL | PostgreSQL connection string |
--log-level | info | Log level: trace, debug, info, warn, error |
1
orcher server stop [OPTIONS]
2
3
# Examples
4
orcher server stop
5
orcher server stop --force --timeout 10
| Option | Default | Description |
|---|
-f, --force | false | Force shutdown |
--timeout | 30 | Graceful shutdown timeout (seconds) |
1
orcher server status [OPTIONS]
2
3
# Examples
4
orcher server status
5
orcher server status --verbose --output json
| Option | Default | Description |
|---|
-v, --verbose | false | Show detailed status |
-o, --output | table | Output format |
--grpc-addr | http://localhost:50051 | gRPC address to check |
--orchestrator-http | http://localhost:8080 | Engine HTTP health address |
1
orcher server restart [OPTIONS]
| Option | Description |
|---|
-f, --force | Force restart |
Shows version information for the CLI and the running engine.
Manage namespaces for multi-tenancy.
1
orcher namespace create <name> [OPTIONS]
2
3
# Examples
4
orcher namespace create production
5
orcher namespace create staging --description "Staging env" --retention-days 14 --owner-email team@example.com
6
orcher namespace create dev --data env=development --data tier=free
| Option | Default | Description |
|---|
-d, --description | — | Human-readable description |
-r, --retention-days | 7 | Data retention period |
-e, --owner-email | — | Owner email |
--data | — | Key-value metadata (repeatable) |
1
orcher namespace list [OPTIONS]
| Option | Default | Description |
|---|
-l, --limit | 100 | Max results |
--offset | 0 | Pagination offset |
1
orcher namespace get <name>
1
orcher namespace update <name> [OPTIONS]
2
3
# Example
4
orcher namespace update staging --retention-days 30 --owner-email newteam@example.com
| Option | Description |
|---|
--description | Updated description |
--owner-email | Updated owner email |
--retention-days | Updated retention period |
--data | Updated key-value metadata |
1
orcher namespace deprecate <name> [--force]
1
orcher namespace delete <name> [--force]
View and manage task queues.
1
orcher queue list [OPTIONS]
2
3
# Examples
4
orcher queue list
5
orcher queue list --queue payment-tasks --all-namespaces
| Option | Default | Description |
|---|
-Q, --queue | — | Filter by queue name |
-A, --all-namespaces | false | Show across all namespaces |
-l, --limit | 50 | Max results |
1
orcher queue stats <queue_name> [OPTIONS]
2
3
# Example
4
orcher queue stats payment-tasks --type payment-workflow
| Option | Description |
|---|
-t, --type | Filter by workflow type |
1
orcher queue depth [queue_name] [OPTIONS]
2
3
# Examples
4
orcher queue depth payment-tasks
5
orcher queue depth --watch --interval 5
| Option | Default | Description |
|---|
-w, --watch | false | Continuous monitoring mode |
--interval | 2 | Watch update interval (seconds) |
1
orcher queue pollers <queue_name> [OPTIONS]
| Option | Description |
|---|
-v, --verbose | Show detailed poller information |