The cloe-launch
script is a stop-gap till the Cloe CLI (run as just cloe
)
makes it into the repository.
We recommend the use of pipx for installation, but you can also use
pip. The easiest way is to just use the Makefile
:
make install
cloe-launch [-v] config [--edit] [--write]
cloe-launch [-v] clean CONANFILE
cloe-launch [-v] prepare CONANFILE [CONAN_INSTALL_ARGS]
cloe-launch [-v] activate [-c] CONANFILE [CONAN_INSTALL_ARGS]
cloe-launch -v activate -c tests/conanfile.py -o cloe-engine:server=True
cloe-launch [-v] deploy [-D PATH] CONANFILE [CONAN_INSTALL_ARGS]
cloe-launch [-v] exec [-c] [-e VAR] [-E] [-d] CONANFILE [CONAN_INSTALL_ARGS] -- [ENGINE_ARGS]
cloe-launch exec tests/conanfile.py -o cloe-engine:server=False -- -l debug run
cloe-launch [-v] shell [-c] [-e VAR] [-E] CONANFILE [CONAN_INSTALL_ARGS] -- [SHELL_ARGS]
The CLI interface to cloe-engine
should do as little as possible and as much
as necessary. The order of operations should be clear.
- Convert YAML to JSON (not implemented yet)
- Relay STDIN and anonymous files
- Generate runtime environment from profile
- Run cloe-engine
There are two main sources for combining plugins and data: local and containerized. It should be possible to transparently combine these. This will require replacing the profile format. It will probably also require extending and refining the module.py plugin configuration method.
This is what still needs to be done:
- Merge with Cloe CLI
- Finalize module.py design
- Allow combination of multiple sources
One of the main use-cases of cloe-launch is to run a federation of Cloe Conan
packages. As such, we'd like to make use of the local instance of this Python
module without resorting to installing it first. This is possible by setting
the PYTHONPATH
variable and using the cloe_launch
module:
PYTHONPATH="${CLOE_ROOT}/cli" python -m cloe_launch