scalio-platform
Shared building blocks of the Scalio apps (Nexus, Compass, Citadel, Foundry, Rosetta, Pulse, Beacon, Cockpit, ID, Monitor). Before this package each app kept its own copy of these files (architecture review C2/C4, ADR 0058 in scalio-docs). Nothing in this package is secret.
| Module | What it does |
|---|---|
scalio_platform.job_lease |
Runs a background loop on one instance at a time (lease in db.job_leases). During an update two instances run side by side; without the lease both would act. |
scalio_platform.migrations |
Schema migrations for MongoDB: ordered steps, each applied once, version in db.meta (schema_version). |
scalio_platform.health |
The answer of GET /api/health that Scalio Monitor reads (ok / degraded / down, leases of the loops). |
scalio_platform.error_report |
Sends unexpected errors to Scalio Monitor, only when ERROR_REPORT_URL and ERROR_REPORT_TOKEN are set. |
scalio_platform.app_links |
Links and features of the product switcher (SCALIO_APP_LINKS, SCALIO_STAGE, SAAS_MODE). |
scalio_platform.setup_wizard |
State of the Einrichtungsassistent (GET/PUT /api/setup/wizard, ADR 0060): wizard_state, save_wizard, parse_update. |
Use in an app
scalio-platform==0.1.0 # backend/requirements.txt, exact version
from scalio_platform import error_report, health, job_lease
from scalio_platform.migrations import BASELINE, run_migrations
MIGRATIONS = BASELINE # append (2, migrate_002_...) and so on, never edit past steps
async def startup():
await run_migrations(db, MIGRATIONS) # before the background loops
for name, loop in LOOPS.items():
asyncio.create_task(job_lease.run_exclusive(db, name, loop))
error_report.install(app, "citadel", build_info)
code, body = await health.health_report(db, build_info(), lease_jobs=sorted(LOOPS))
A migration step must be safe to run twice: two instances can start at the same moment.
Develop and release
pip install -e ".[dev]", thenpytest -qandruff check .(both run in CI).- Release: bump
pyproject.tomland__version__, add the CHANGELOG entry, merge, then «Freigeben» in the Scalio Cockpit (workflowpublish.yml: PyPI with trusted publishing, tag and GitHub release). Tags withoutv. - A change of behaviour changes every app on its next upgrade: say so in the PR and the CHANGELOG.
Metadata
Release files for scalio-platform 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 | Provenance | Actions |
|---|---|---|---|---|
| scalio_platform-0.2.0.tar.gz | 19.1 kB | With provenance | Details for scalio_platform-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scalio_platform-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for scalio_platform-0.2.0-py3-none-any.whl |
Total release size: 33.3 kB
Release files / scalio_platform-0.2.0.tar.gz
| Download URL | scalio_platform-0.2.0.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8b8252794211f13d66978ad23407c1a33eb4d9d614d4ae709458157e38821b2
|
|
BLAKE2b-256 checksum How to use checksums |
e1fb186468cc89a14106954182d9ac4e29ec356598e621350d3ddf0a6ec2b212
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logRelease files / scalio_platform-0.2.0-py3-none-any.whl
| Download URL | scalio_platform-0.2.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e724e1e1dc4a32a2c2add8c5e2aa14cc1171a1302c74276b513d1f258a6908b
|
|
BLAKE2b-256 checksum How to use checksums |
94ff1b5e53b762c88951140eecd2c60b5788ddba359453f574591eac545172d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logSecurity for scalio-platform 0.2.0
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 scalio_platform-0.2.0.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 Nov 1, 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.