Exordos CLI
📚 CLI Documentation: exordos.github.io/exordos | 📚 Platform Documentation: exordos.github.io/exordos_core
Exordos CLI is the official command-line interface for the Exordos Core platform. It provides a unified toolset for managing the full lifecycle of Exordos projects — from building and provisioning elements to bootstrapping installations, managing backups, and interacting with a running Exordos Core environment.
🚀 To start using Exordos
Install the CLI with a single command:
curl -fsSL https://repo.exordos.com/install.sh | sh
What Exordos CLI does
Exordos CLI bridges the gap between your local development environment and the Exordos Core platform. With a self-contained installation you can:
- Build projects — compile Exordos project images and artifacts from a declarative
exordos.yamlconfiguration. - Bootstrap installations — spin up local virtual machine environments from built images for development and testing.
- Manage installations — connect via SSH, list, and remove running Exordos instances.
- Interact with the platform — manage elements, IAM, secrets, compute nodes, realms, and more through a rich set of subcommands.
- Automate backups — run periodic or one-shot backups of installations with compression, encryption, rotation, and disk-overflow protection.
For a full overview of all commands and configuration options, visit the documentation.
💡 Contributing
Contributing to the project is highly appreciated! However, some rules should be followed for successful inclusion of new changes in the project:
- All changes should be done in a separate branch.
- Changes should include not only new functionality or bug fixes, but also tests for the new code.
- After the changes are completed and tested, a Pull Request should be created with a clear description of the new functionality. Add one of the project maintainers as a reviewer.
- Changes can be merged only after receiving approval from one of the project maintainers.
Local test environment on Ubuntu
The test environments require a working Python 3 installation. Check both command names:
python3 --version
python --version
If python3 works but the unversioned python command is missing, install Ubuntu's compatibility package:
sudo apt update
sudo apt install python-is-python3
python-is-python3 only provides the python -> python3 link; it does not install Python 3 itself.
Tox uses uv for environment creation. In a sandbox or another restricted environment where ~/.cache/uv is read-only, point the cache to a writable temporary directory:
UV_CACHE_DIR="${TMPDIR:-/tmp}/uv-cache" tox -e develop
Release files for exordos 3.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| exordos-3.2.6.tar.gz | 512.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| exordos-3.2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 912.7 kB
Release files / exordos-3.2.6.tar.gz
| Download URL | exordos-3.2.6.tar.gz |
|---|---|
| Size | 512.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b3d67682339ebbe6564e93030344ee1ac3eec56fd7985741b86fa3ac085750e
|
|
BLAKE2b-256 checksum How to use checksums |
f214476e798182d21d8d58604c9bd4a25244ffa4a5bf55f44570abfcbf71d804
|
| 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 Sep 10, 2026.
Transparency logRelease files / exordos-3.2.6-py3-none-any.whl
| Download URL | exordos-3.2.6-py3-none-any.whl |
|---|---|
| Size | 399.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac5dd42afebf06f0c8ff447ccfd10c7e3ac41ea7064e2d41d5f2078eb79c34a3
|
|
BLAKE2b-256 checksum How to use checksums |
4c640f766f89123249983ca25c4665bccb620dfdc7164f007f825c4882209bd6
|
| 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 Sep 10, 2026.
Transparency log
