ibek
ibek is the IOC builder for epics-containers. It combines reusable support definitions with an IOC instance's YAML to generate its startup script and database substitutions. A generic IOC image supplies the compiled EPICS support; instance configuration selects what that image runs.
The CLI supports several stages of that workflow:
| Where | Commands | Purpose |
|---|---|---|
| Container build | ibek support, ibek ioc |
Prepare support, schemas and generic IOC assets. |
| Running IOC container | ibek runtime |
Generate startup files, databases and related runtime assets. |
| Development container | ibek dev |
Connect an IOC instance checkout to the development environment. |
| Services checkout, outside the IOC container | ibek pattern |
Vendor runtime patterns and compose the instance schema. |
See the CLI reference for individual commands and exceptions to these groupings.
Install the standalone CLI with Python 3.13 or later:
uv tool install ibek
ibek --help
EPICS build and runtime operations also need the tools and directory layout provided by the appropriate IOC container.
Read the documentation for a small rendering tutorial, YAML and Jinja references, and how ibek uses ibek-support. For creating and deploying complete IOCs, use the epics-containers documentation.
Metadata
Release files for ibek 4.11.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 |
|---|---|---|---|---|
| ibek-4.11.1.tar.gz | 423.1 kB | Without provenance | Details for ibek-4.11.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ibek-4.11.1-py3-none-any.whl | Python 3 | none | any | Details for ibek-4.11.1-py3-none-any.whl |
Total release size: 530.3 kB
Release files / ibek-4.11.1.tar.gz
| Download URL | ibek-4.11.1.tar.gz |
|---|---|
| Size | 423.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
465d2c93b4bfcbb2c607fe3f7c30a7ff42419abdbbfbe3d8af827969ea942b10
|
|
BLAKE2b-256 checksum How to use checksums |
4b4c1747395796ca0690b72cf106ad578947fbfeda84c2644b8c3a4dcf1fd154
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / ibek-4.11.1-py3-none-any.whl
| Download URL | ibek-4.11.1-py3-none-any.whl |
|---|---|
| Size | 107.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7591c46b82a0503fdf9818e54a2837ab6a1d4f28ff2a42f1691b7a23377e3556
|
|
BLAKE2b-256 checksum How to use checksums |
289b208cc85320a2dd4845ad32622108702c957799f66c60d0a0f49cccc5316a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for ibek 4.11.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
