# Toolkit Socket

The Toolkit socket is a local/shared Socket.IO authoring server for browser-only Toolkit workflows.

## Local Development

```bash
npm run dev:toolkit
curl http://127.0.0.1:5174/health
```

Default local settings:

- host: `127.0.0.1`
- port: `5174`
- CORS origin: `http://127.0.0.1:5173`

## Shared Deployment

The deployed browser app at `http://bone-kingdom.tabitha.tealthrone/` connects to:

```text
http://bone-kingdom.tabitha.tealthrone:5174
```

Woodpecker restarts this socket from the shared repo workspace with:

```bash
TOOLKIT_SOCKET_HOST=0.0.0.0 \
TOOLKIT_SOCKET_PORT=5174 \
TOOLKIT_SOCKET_CORS_ORIGIN='http://127.0.0.1:5173,http://localhost:5173,http://bone-kingdom.tabitha.tealthrone' \
sh scripts/deploy/restart-toolkit-socket.sh
```

Running from the repo workspace is intentional. Toolkit edits made from the deployed browser update the same source files used during development:

- `src/data/toolkit/*.json`
- `src/assets/images/uploads/`
- `src/assets/music/uploads/`

The deploy script syncs socket code and scripts, but uses `--ignore-existing` for Toolkit JSON and uploaded assets so live content edits are not overwritten by routine deploys.