MirrorDash SDK
Build modules for MirrorDash: small panels on the mirror, such as weather, a calendar or your own data.
Quick start
You need uv. Then one command creates a module, sets up a local mirror with it, starts it and opens it in your browser:
uvx mirrordash-sdk quickstart mirrordash-my-widget
The module shows example data right away. Change it in mirrordash-my-widget/mirrordash_my_widget/; restart with uvx mirrordash-sdk start (inside the module directory) to see your changes. The admin page of this local mirror is at http://localhost:8000/admin, password mirrordash.
Templates
| Template | For a module that… | |
|---|---|---|
api (default for quickstart) |
fetches data from a web API with an API key and shows a value and a few rows | --template api |
basic |
works out what to show by itself, without the internet | --template basic |
Both show their data with the mirror's own building blocks (big numbers, label–value rows, messages), so they need no CSS, and both come with tests (uv run pytest).
Commands
uvx mirrordash-sdk quickstart <name> [-t api|basic] # everything below in one go
uvx mirrordash-sdk create-module <name> [-t basic|api] # just create the module
uvx mirrordash-sdk dev-setup -e # a local mirror (.venv) with this module on it
uvx mirrordash-sdk start # start the local mirror: http://localhost:8000/
uvx mirrordash-sdk validate . # check the module before you publish it
uvx mirrordash-sdk build # build the package
uvx mirrordash-sdk publish # validate and upload to PyPI
Learn more
- MODULE_GUIDE.md: the reference: the plugin class,
fetch_json, settings, translations, the building blocks, publishing. - MODULE_AGENTS.md: the same rules, short, for AI coding agents.
http://localhost:8000/designwhile your local mirror runs: every building block with markup to copy.
Developing the SDK itself
uv sync && uv run pytest # the tests also generate every template and run its tests
Releases: python3 scripts/release.py (try --dry-run first). It checks master and the tests, sets the version, pushes and tags vX.Y.Z; GitHub Actions then tests, builds and publishes it to PyPI.
Metadata
Release files for mirrordash-sdk 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mirrordash_sdk-0.2.0.tar.gz | 40.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mirrordash_sdk-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.5 kB
Release files / mirrordash_sdk-0.2.0.tar.gz
| Download URL | mirrordash_sdk-0.2.0.tar.gz |
|---|---|
| Size | 40.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86c9ca58ace72dae203ab1edf059d9d1051f31e5f05d2cf5695268d12fcbaeef
|
|
BLAKE2b-256 checksum How to use checksums |
7c6adc6d476b2690ef319dfd2714d1856630d36ecb483b1c4be4a54bec995f53
|
| 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 8, 2026.
Transparency logRelease files / mirrordash_sdk-0.2.0-py3-none-any.whl
| Download URL | mirrordash_sdk-0.2.0-py3-none-any.whl |
|---|---|
| Size | 28.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99ba4ffcd5f3740f159c9d719a1d1ecc37cb9f351e74f8292bce7fa0bef643b8
|
|
BLAKE2b-256 checksum How to use checksums |
7cb53ec26ee75b9f7130313d1d0ff7fe31119d58557515e1c20248198329dca4
|
| 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 8, 2026.
Transparency log