binctl
binctl is a tiny graph-based inventory system for people with too many bins, boxes, and shelves.
Instead of thinking in terms of "SKUs" and "stock levels", binctl models your world as:
- nodes - items, bins, shelves, rooms, etc.
- edges - "this thing lives inside that thing".
It's backed by a Flask API with a CLI frontend.
Install from PyPI
pip install binctl-server
Install database drivers only when needed:
- MySQL:
pip install 'binctl-server[mysql]' - PostgreSQL:
pip install 'binctl-server[postgresql]'
Quickstart (SQLite, local dev)
The fastest path to a running system. Requires Python 3.11+. Run each block in your terminal:
# 1. Generate the ignored API client
./genclient.sh
# 2. Create and activate a virtual environment
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
# 3. Install dependencies — binctl-client is installed from PyPI
pip install -e .
# 4. Configure the database — copy .env.example and uncomment the SQLite line
cp .env.example .env
# In .env, uncomment: DATABASE_URL=sqlite:///binctl.db
# 5. Initialize the database
python manage.py init-db
# 6. Create a user and get a token
python manage.py create-user alice --token
# → prints something like: token: abc123...
export TOKEN=<paste token here>
# 7. Start the server (keep this terminal open, or run it in the background)
uvicorn web:create_app --factory
# 8. In another terminal (with .venv activated), verify it works
binctl --token $TOKEN node list
Setup
-
Generate the API client, then create and activate a virtual environment and install dependencies:
./genclient.sh python3 -m venv .venv source .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e .binctl-clientis installed from PyPI.genclient.shusesuvxto generate a local client fromopenapi.yamlas an API-contract check; itsbinctl-client/output is ignored and must not be committed.If you need MySQL or PostgreSQL support, install the optional driver afterward:
- MySQL:
pip install pymysqlorpip install 'binctl-server[mysql]' - PostgreSQL:
pip install psycopg2-binaryorpip install 'binctl-server[postgresql]' - SQLite — no extra driver needed, skip this step.
- MySQL:
-
Copy
.env.exampleand set your database URL:cp .env.example .envSupported URL formats:
- SQLite:
sqlite:///binctl.db - MySQL:
mysql+pymysql://user:password@localhost/binctl - PostgreSQL:
postgresql+psycopg2://user:password@localhost/binctl
The server and
manage.pyload.envautomatically — no manualexportneeded. - SQLite:
-
Initialize the database:
python manage.py init-db -
Start the server:
uvicorn web:create_app --factory -
Create a user:
- With a non-expiring API token (recommended for scripts):
python manage.py create-user alice --token - With a password (for browser/interactive use):
python manage.py create-user alice --password <password>
Then pass
--token <token>(or--username/--password) tobinctlcommands. - With a non-expiring API token (recommended for scripts):
CLI
binctl node list|get|create|update|delete- manage nodesbinctl tag list|get|create|update|delete- manage tags
Key flags for binctl:
| Flag | Description |
|---|---|
--base-url |
API server URL (default: http://localhost:5000) |
--token |
Bearer token (preferred) |
--username / --password |
Login-based auth |
manage.py subcommands (server-side user/token management):
python manage.py init-db- initialize the database schemapython manage.py create-user <username> --password <p>- create a user with a passwordpython manage.py create-user <username> --token- create a passwordless user and emit a non-expiring tokenpython manage.py set-password <username>- interactively set a new password for a userpython manage.py list-users- list userspython manage.py list-tokens <username>- list tokens for a userpython manage.py revoke-tokens <username>- revoke all tokens for a user
Example: Building an inventory
This walks through creating a hierarchy (room → shelf → item), listing it, and moving a node.
Node IDs are opaque strings (e.g. wGIDjZ0AAC), not sequential integers. Copy them from the
output of each command — do not guess or construct them by hand.
export TOKEN=<your token>
# Create a room (a container)
binctl --token $TOKEN node create --label "Garage" --is-container
# → {"id": "wGIDjZ0AAC", "label": "Garage", "is_container": true, ...}
# Create a shelf inside the room — use the id from the previous output
binctl --token $TOKEN node create --label "Shelf A" --is-container --parent-id wGIDjZ0AAC
# → {"id": "xK3mPq1BBD", "label": "Shelf A", ...}
# Add an item to the shelf
binctl --token $TOKEN node create --label "Power drill" --parent-id xK3mPq1BBD
# → {"id": "yR7nTs2CCE", "label": "Power drill", ...}
# List everything
binctl --token $TOKEN node list
# Move the drill to a different shelf (use that shelf's id from its create output)
binctl --token $TOKEN node update --node-id yR7nTs2CCE --parent-id <other-shelf-id>
# Detach the drill entirely (no parent, becomes a root node)
binctl --token $TOKEN node update --node-id yR7nTs2CCE --no-parent
Running as a service
A systemd unit file is shipped at systemd/binctl-server.service
for running the server persistently on a Linux host. Copy it to /etc/systemd/system/, adjust the
paths/user, then systemctl daemon-reload && systemctl enable --now binctl-server. See
Server administration for the full walkthrough.
Security
binctl is not designed to be exposed to the internet. It is intended for use on trusted local or private networks. Security bugs will be fixed when found, but the threat model assumes a trusted network environment.
If you must expose the server to untrusted networks, place a reverse proxy such as nginx or Caddy in front of it to handle:
- SSL/TLS termination — the Flask/uvicorn server does not handle TLS on its own.
- Rate limiting on
POST /v1/auth/login— scrypt makes each login attempt slow, but a determined attacker can still brute-force credentials over time without a request rate limit.
Token security — tokens created via the login API (web/browser sessions) expire after 30 days by default; set SESSION_LIFETIME_DAYS to override. Tokens created via python manage.py create-user do not expire by default. All tokens should be treated with the same secrecy as a password: store them safely, do not share them, and revoke compromised tokens promptly with python manage.py revoke-tokens.
Password policy — set-password enforces a minimum of 6 characters. No other complexity requirements are enforced by the application. Choose a strong password of at least 16 characters using a mix of uppercase letters, lowercase letters, digits, and symbols.
Development (uv)
Contributors can use uv for a faster workflow. Generate the
ignored local client first, then install the published binctl-client package and other
development dependencies.
# Install uv (skip if already installed)
curl -LsSf https://astral.sh/uv/install.sh | sh
# Generate the client from the API contract
./genclient.sh
# Install all dependencies including dev tools
uv sync
# Run checks
uv run pytest
uv run ruff check
uv run ty check
Tests / CI
The following must pass before merging (run with the venv activated):
pytest
ruff check
ty check
Publishing releases
In GitHub Actions, run the Publish to PyPI workflow and select the patch,
minor, or major version increment. The workflow runs from main, uses
uv version --bump to update pyproject.toml and uv.lock, commits the new
version, creates and pushes its matching v<version> tag, and publishes that
version to PyPI.
Before the first release, configure PyPI Trusted Publishing for
clueboard/binctl with workflow filename publish.yml and environment name
pypi. The workflow uses GitHub Actions OIDC, so it does not require a PyPI
API token or repository secret.
Concepts
Nodes
Everything is a node:
- items (tools, parts, one-off widgets)
- containers (bins, boxes, drawers)
- higher-level containers (shelves, rooms, buildings)
Nodes live in the nodes table:
id- BIGINT primary keylabel- human-readable namedescription- optional free textis_container-TRUEif this node can contain children
Edges
Containment is modeled via the edges table:
parent_id→child_id- each child has at most one parent (enforced by a UNIQUE constraint)
- self-loops are rejected (
parent_id <> child_id)
This gives you a forest of trees:
- top-level nodes (rooms, "unplaced items") have no parent
- containers and items have exactly one parent
- containers can have many children
When you delete a container, any direct children can be reassigned by setting ORPHAN_LOCATION in your .env. The server looks up a container by that label at delete time, and if none exists outside the deleted subtree it creates a new root container with that label automatically.
Tags
Tags are stored in tags + tag_node for future filtering and categorization.
Tags are exposed via binctl tag list|get|create|update.
Troubleshooting
ModuleNotFoundError: No module named 'binctl_client'
Reinstall the project dependencies with pip install -e . or uv sync.
Connection refused / Failed to connect when running binctl commands
The server is not running. Start it with uvicorn web:create_app --factory (binds to
http://localhost:5000 by default). If you changed the port, pass --base-url http://localhost:<port>
to binctl.
401 Unauthorized
Token is missing or wrong. Re-create one with python manage.py create-user alice --token,
or list existing tokens with python manage.py list-tokens alice.
DATABASE_URL not set or database errors on startup
Export the variable before running server or manage commands:
export DATABASE_URL=sqlite:///binctl.db
Or add it to your .env file (copied from .env.example).
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file binctl_server-1.0.0.tar.gz.
File metadata
- Download URL: binctl_server-1.0.0.tar.gz
- Upload date:
- Size: 37.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
ae8c3d303a6e7315be9b570e829d119afa756baf30e9d1434f45063b37f5a266
|
|
| MD5 |
0f195c26222365105692f9cec3179c06
|
|
| BLAKE2b-256 |
986c87baccc350c18c7f99ed59aaf2ff331743517dd97bc55b83959ee2b11405
|
Provenance
The following attestation bundles were made for binctl_server-1.0.0.tar.gz:
Publisher:
publish.yml on clueboard/binctl
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
binctl_server-1.0.0.tar.gz -
Subject digest:
ae8c3d303a6e7315be9b570e829d119afa756baf30e9d1434f45063b37f5a266 - Sigstore transparency entry: 2298652766
- Sigstore integration time:
-
Permalink:
clueboard/binctl@5fcbf7eb21b9e005d52f687d3a0a2af78c64a00a -
Branch / Tag:
refs/heads/main - Owner: https://github.com/clueboard
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@5fcbf7eb21b9e005d52f687d3a0a2af78c64a00a -
Trigger Event:
workflow_dispatch
-
Statement type:
File details
Details for the file binctl_server-1.0.0-py3-none-any.whl.
File metadata
- Download URL: binctl_server-1.0.0-py3-none-any.whl
- Upload date:
- Size: 24.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a0f6d32b88d1a387d2e7dc7a5797ffe96aa109e9a60877b74016143fa2779a2a
|
|
| MD5 |
505a476a07b24536fd9b0e838bf2d3da
|
|
| BLAKE2b-256 |
38a4557d169bad7a1905ba15666223940f8ab4c7b92ab3aa79916a6a670e5bd4
|
Provenance
The following attestation bundles were made for binctl_server-1.0.0-py3-none-any.whl:
Publisher:
publish.yml on clueboard/binctl
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
binctl_server-1.0.0-py3-none-any.whl -
Subject digest:
a0f6d32b88d1a387d2e7dc7a5797ffe96aa109e9a60877b74016143fa2779a2a - Sigstore transparency entry: 2298652814
- Sigstore integration time:
-
Permalink:
clueboard/binctl@5fcbf7eb21b9e005d52f687d3a0a2af78c64a00a -
Branch / Tag:
refs/heads/main - Owner: https://github.com/clueboard
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@5fcbf7eb21b9e005d52f687d3a0a2af78c64a00a -
Trigger Event:
workflow_dispatch
-
Statement type: