Skip to content
TalesMUD

Build from Source

Build from Source

Section titled “Build from Source”

Makefile Targets

Section titled “Makefile Targets”
Terminal window
make build              # Build everything (frontend + backend)
make build-frontend     # Build admin UI (Vite → dist)
make build-mud-client   # Build game client (Vite → dist)
make build-backend      # Compile Go binary
make run-server         # Run the Go server
make run-frontend       # Start admin UI Vite dev server
make run-mud-client     # Start game client dev server
make run                # Run all three concurrently

Build Process

Section titled “Build Process”

1. Build the Admin Frontend

Section titled “1. Build the Admin Frontend”
Terminal window
cd public/app
npm install
npm run build
cd ../..

Output: public/app/dist/ — compiled Svelte + Vite assets

2. Build the Game Client

Section titled “2. Build the Game Client”
Terminal window
cd public/mud-client
npm install
npm run build
cd ../..

Output: public/mud-client/dist/ — compiled Svelte + xterm.js assets

3. Build the Go Binary

Section titled “3. Build the Go Binary”
Terminal window
go build -o talesmud ./cmd/tales/

The Go binary embeds both frontend dist/ directories using Go’s //go:embed directive. This means the compiled binary is self-contained — no separate static files needed.

Docker Build

Section titled “Docker Build”
Terminal window
docker build -t talesmud:latest .

The Dockerfile runs all three build steps sequentially.

Next Steps

Section titled “Next Steps”