Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Bedrock Server Manager UI

This is the React frontend for Bedrock Server Manager, packaged as a Python library.

Installation

pip install bsm-frontend

Usage

from bsm_frontend import get_static_dir

static_files_path = get_static_dir()
print(f"Static files are located at: {static_files_path}")

OpenAPI contract

Install bedrock-server-manager from the target backend checkout. Export with python -m bedrock_server_manager.web.contract --output frontend/src/api/generated/openapi.json, then run npm run api:generate in frontend. CI compares the complete document with backend dev using the backend-owned exporter and its declared dependencies.

Application monitor

The Metrics view groups application performance, host utilization, runtime activity, and Bedrock processes. CPU and memory charts show recent observations using your preferred units. Pause updates to freeze the displayed snapshot; backend collection continues. History is held in backend memory and resets on restart. Missing measurements appear as a dash, not zero.

Administrators can also open Diagnostics on a backend with the diagnostics API:

  • Overview: readiness, health, findings, and subsystem status at a glance.
  • Subsystems: concise observations with expandable technical details and source timing. Search registered plugins and inspect their runtime status and owned work.
  • History: filter and page retained records across restarts, then inspect correlated events, tasks, and records. Sources report availability independently.
  • Advanced: inspect collector and installation metadata, save an in-memory comparison baseline, and compare fresh observations. Counter deltas are suppressed across restarts.

Refresh manually or enable a 15-second interval while Diagnostics is open. Unknown plugin status means the backend could not resolve its runtime status; it does not prove the plugin is loaded. Missing timestamps mean no corresponding timestamp was reported. Stale observations retain their source timing.

Download an authenticated support report and review it before sharing. Baselines and reports are not saved in browser storage. Leaving Diagnostics discards the baseline; account/session changes invalidate pending work. History requests start only when you open History.

Metadata

Release files for bsm-frontend 1.3.0b4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bsm-frontend 1.3.0b4
File Size Uploaded
bsm_frontend-1.3.0b4.tar.gz 41.3 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for bsm-frontend 1.3.0b4
File Interpreter ABI Platform
bsm_frontend-1.3.0b4-py3-none-any.whl Python 3 none any Details

Total release size: 62.0 MB

Release files / bsm_frontend-1.3.0b4.tar.gz

Download URL bsm_frontend-1.3.0b4.tar.gz
Size 41.3 MB
Tags Source
SHA-256 checksum
How to use checksums
c54fda90f92a170d66294008140307a10c5f8ad7d449561a60cac2dda538762b
BLAKE2b-256 checksum
How to use checksums
4c0f5f1f7940b76801159d72d4f52db84992f37105fd136144ddf499505511d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / bsm_frontend-1.3.0b4-py3-none-any.whl

Download URL bsm_frontend-1.3.0b4-py3-none-any.whl
Size 20.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
12c88abcde2740eb84c76de51821fd4fe4c992447aab349c6d07a4dc519a5c49
BLAKE2b-256 checksum
How to use checksums
e2e2ac627fe20a1e5234edbb53d8f0422c3c484e13d55940421a48f3b0c924b9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page