Hive

Hivegame is a free online hive game server focused mostly on realtime gameplay and ease of use.

It is written in rust nightly and relies on the Leptos framework. Pure hive logic is inside the engine workspace.

It also inclides Hive-hydra, an application to integrate Hivegame with any UHP (Universal Hive Protocol) AIs.

Development

Prerequisites (skip if using Nix)

1. Setup the Rust Toolchain

• Install the Rust toolchain.
• Set the default toolchain to nightly from the project root:

rustup override set nightly

• Alternatively set the default toolchain to nightly globally:

rustup default nightly

• Add the WebAssembly target:

rustup target add wasm32-unknown-unknown

2. Install Leptos

cargo install cargo-leptos

3. Install and Setup PostgreSQL

• Follow the installation instructions for your OS (example for Arch Linux).
• Edit hba.conf to host all all local 127.0.0.1/32 trust (to allow passwordless login).
• With PostgreSQL running, create the development and test databases with hive-dev as the owner:

sudo -u postgres createuser hive-dev
sudo -u postgres createdb -O hive-dev hive-local
sudo -u postgres createdb -O hive-dev hive-test

Manual Setup (Without Nix)

1. Install Diesel CLI with PostgreSQL support

cargo install diesel_cli --no-default-features --features postgres

2. Install Leptos Formatter

cargo install leptosfmt

3. Run Database Migrations

• From the project root, navigate to db and run migrations:

cd db && diesel migration run && cd ..

4. Run the Project

• The watch command will recompile your code when files change and serve it on localhost::3000, static changes inside the view! macro won't cause a recompile if running with the --hot-reload flag

cargo leptos watch --hot-reload

5. Before Making a Pull Request please clippy and format your code

cargo clippy --fix --all-features && leptosfmt apis -q && cargo fmt

Alternative to the manual setup use Nix

1. Install Nix or just run:

curl -L https://nixos.org/nix/install | sh -s -- --daemon

• Add these experimental features to your nix config (/etc/nix/nix.conf)

experimental-features = nix-command flakes

2. Start the development shell

nix develop -c $SHELL

3. Init and Start the PostgreSQL DB

pg-start

This creates both hive-local and hive-test.

4. Now start the server

migration run
server

5. Start Hive-hydra to play with Bots

You need to setup bot users in Hive. See hive-hydra/hive-hydra.yaml

hive-hydra

5. Stop PostgreSQL

pg-stop

4. (Optional) Setup direnv
5. Before committing code please run

format

Docker Development

Ensure docker is installed on your machine. You can run the following command to start the server and database:

docker compose up --build -d

This command downloads and installs the required dependencies. The first time you run this command, it may take a few minutes to complete.

# to stop docker compose
docker compose down

# if you have already built the image, you can save some time by running without the build flag:
docker compose up -d

This will create hive-local and hive-test, apply migrations and run the app on localhost:3000. If you already have an older hive-dev Docker volume, create the test database with docker compose exec postgres createdb -U hive-dev -O hive-dev hive-test, or recreate the volume with docker compose down -v if you do not need the existing local data.

Once the containers are up, follow the app logs to watch cargo-leptos compile and see when the server is actually serving:

docker compose logs -f app

This shows the incremental build output and prints when the server binds to the port.

WebSocket telemetry

The server publishes a snapshot of WebSocket-related counters and gauges (connections, dispatches, drops, queue depth, chat sizes, process memory, etc.) on a fixed interval. Each snapshot is written to the log and, if a CSV file path is configured, appended as one row to that file.

Defaults

• Release builds: telemetry is on. Default interval 30s. Default CSV path ./ws_metrics.csv (relative to the server's working directory).
• Debug builds: opt-in. The job only runs if WS_TELEMETRY_INTERVAL_SECS is set; the CSV is only written if WS_METRICS_LOG_FILE is set.

Environment variables

• WS_TELEMETRY_INTERVAL_SECS
  • Set to 0 to disable the snapshot job entirely.
  • Set to a positive integer to override the interval. Values below 10s are accepted but log a warning — the snapshot walks every chat channel and contends with WS traffic for chat locks at sub-10s intervals.
• WS_METRICS_LOG_FILE
  • Set to an empty string to keep snapshots running but skip CSV writing.
  • Set to a path to override the default CSV location.

Admin dashboard

Admins can view the data as graphs at /admin/telemetry. The page reads the configured CSV file, supports a time-range selector (last hour / 24h / 7d / all), a manual refresh button, and auto-refreshes every 30s.

Troubleshooting

If you get an error of the form

 it looks like the Rust project used to create this Wasm file was linked against
 version of wasm-bindgen that uses a different bindgen format than this binary:
 
   rust Wasm file schema version: 0.2.93
      this binary schema version: 0.2.95
 

That means that the Cargo.lock file was built with a different version of cargo-leptos than your current one. You have two options to fix this. Either update cargo-leptos as the lock file was probably created by a newer version than you have or delete the lock file.

License

This source code with the exception of the graphics is licensed under the GNU Affero General Public License 3 license found in the LICENSE.md file in the root directory of this project. The official graphics for Hive are owned by Gen42 and may not be used without prior written consent.