manabrew-server 0.9.1

Matchmaking and lobby relay server for manabrew multiplayer
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74

# Forge Server

WebSocket-based game lobby server for Forge.

## Running with Docker

```bash
# From this directory (manabrew-rs/crates/manabrew-server/)

# Start the server
docker compose up -d

# View logs
docker compose logs -f

# Stop the server
docker compose down
```

The server listens on **ws://localhost:9443** by default.

## Configuration

All config is via environment variables. Edit `compose.yml` or pass overrides:

| Variable              | Default                | Description               |
| --------------------- | ---------------------- | ------------------------- |
| `FORGE_HOST`          | `0.0.0.0`              | Bind address              |
| `FORGE_PORT`          | `9443`                 | Listen port               |
| `FORGE_MAX_ROOMS`     | `100`                  | Max concurrent rooms      |
| `MANABREW_SERVER_KEY` | `forge`                | Server authentication key |
| `RUST_LOG`            | `manabrew_server=info` | Log level filter          |

The `manabrew` web bundle is configured at **build time** via `Dockerfile.web`
build args (the relay endpoint is baked in):

| Build arg                | Default   | Description                                                                                 |
| ------------------------ | --------- | ------------------------------------------------------------------------------------------- |
| `VITE_RELAY_HOST`        | localhost | WebSocket relay host the browser connects to                                                |
| `VITE_RELAY_PORT`        | `9443`    | Relay port                                                                                  |
| `VITE_RELAY_PASSWORD`    | `forge`   | Relay authentication key                                                                    |
| `VITE_HOSTED_AI_ENABLED` | `false`   | Makes the hosted (server-side Java) engine **available** — shows the Settings engine toggle |

**Web "Play vs AI" does not depend on the node by default.** With
`VITE_HOSTED_AI_ENABLED` unset/false, 1v1-vs-AI runs the engine client-side
(WASM) — no `self-hosted-node` required, and the Settings engine toggle is
hidden. Building with `VITE_HOSTED_AI_ENABLED=true` (e.g. on staging) makes the
hosted engine **available**: a per-user **Settings → "Use hosted Java engine"**
toggle appears, and play stays client-side until a user opts in. Run the node too:

```bash
docker compose --profile hosted-ai up    # production: starts the self-hosted-node
```

The node hosts a `hosted` room, which is **not advertised** in the lobby's
human room list (hosted rooms are observer/AI-host rooms); the Play-vs-AI flow
still discovers it server-side. So the node can stay live without cluttering
the lobby.

**Known limitation:** some search prompts that ask for a card by subtype
(e.g. Flamekin Harbinger fetching an Elemental) don't render correctly in the
hosted-Java flow yet.

```bash
# Example: custom port and key
FORGE_PORT=8080 MANABREW_SERVER_KEY=mysecret docker compose up -d
```

## Building without Docker

```bash
cargo build --release -pmanabrew-server
FORGE_PORT=9443 ./target/releasemanabrew-server/
```