tiny_pacs_admin
Administration extension for tiny_pacs: an offline admin CLI and a database-backed device registry.
What it provides
The DeviceStore component — keeps remote DICOM devices in the database, working in tandem with the built-in Devices component. Devices carry a per-device identity policy (none, username, password); auto-added devices receive configurable defaults.
New tiny-pacs subcommands:
tiny-pacs devices list|add|update|remove|echo — manage the devices stored in the database (--format json|yaml supported);
tiny-pacs components list — registry contents with origin (built-in vs providing distribution) and enabled/disabled state;
tiny-pacs db info — schema versions and table row counts;
tiny-pacs storage stats|verify|cleanup — storage usage statistics (--quota exits 2 when exceeded), record/file consistency check and safe cleanup of stuck in-progress records and orphan files (dry run by default, --apply to delete).
Installation
pip install tiny-pacs-admin
or with the convenience extra:
pip install tiny_pacs[admin]
Installing the extension never changes server behaviour: the DeviceStore component stays disabled until enabled in the configuration, and the CLI subcommands are additive.
Configuration
Enable the component and optionally tune the defaults applied to auto-added devices:
components:
DeviceStore:
on: true
default_identity: none # none | username | password
default_port: 11112
The administration commands work offline against the configured database. Administration against SQLite requires a file-based database — set db_name and mode: rwc on the Database component (the in-memory default cannot persist data between command invocations):
components:
Database:
on: true
db_name: pacs.db
mode: rwc
The YAML-configured devices of the Devices component are imported into the database at server start (upsert by AE title), so the configuration remains the source of truth for configured devices. When using DeviceStore, disable auto_add on the Devices component so newly seen devices are only bookkept in the database.
Documentation
See the Administration tutorial in the tiny_pacs documentation.
Metadata
Release files for tiny-pacs-admin 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tiny_pacs_admin-0.1.1.tar.gz | 13.8 kB | With provenance | Details for tiny_pacs_admin-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tiny_pacs_admin-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for tiny_pacs_admin-0.1.1-py3-none-any.whl |
Total release size: 28.6 kB
Release files / tiny_pacs_admin-0.1.1.tar.gz
| Download URL | tiny_pacs_admin-0.1.1.tar.gz |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72cef59c629cc82a05621728b431b6b9a4fb7037f6635376c494e09424226b9f
|
|
BLAKE2b-256 checksum How to use checksums |
9ead86efb86b266f8a37533b1eae2b3bdd6f39142ec48047ecc9a4a35688d041
|
| 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 4, 2026.
Transparency logRelease files / tiny_pacs_admin-0.1.1-py3-none-any.whl
| Download URL | tiny_pacs_admin-0.1.1-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84e21585fa9274aaedf2dc24bb338d0ef4bc787ba04c3c33b1c38a71eef81d69
|
|
BLAKE2b-256 checksum How to use checksums |
aff42d62a4b108a02b10e576f1846ce67c439ad9fdf86a7a3c55d8764cedd026
|
| 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 4, 2026.
Transparency logSecurity for tiny-pacs-admin 0.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tiny_pacs_admin-0.1.1.tar.gz
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 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.