First Run 2026: test one MLOX install path and interface

[nicococo]

Mission

Help make a first encounter with MLOX boring in the best way: install it through one path, try one or more interfaces, and turn every confusing step into useful feedback or a small fix.

This refreshes the older demo-oriented #4 for the current project: Python 3.11/3.12, three interfaces, multiple distribution paths, and a shared configuration-driven core.

Claim a lane in a comment before starting. You do not need to test the full matrix.

1. Pick an install lane

A. Repository + Task runner

git clone https://github.com/BusySloths/mlox.git
cd mlox
task
task first:steps
conda activate mlox-dev
task tests:unit:run

B. PyPI in a clean environment

python -m pip install busysloths-mlox
mlox --help

C. Docker

Choose either the repository stack or published image:

task docker:up
# cleanup: task docker:down

docker run -it --rm -p 8501:8501 drbusysloth/mlox:latest

2. Pick an interface

From a repository development install, try at least one:

task ui:cli CLI_ARGS="--help"
task ui:streamlit
task ui:textual:terminal

Check startup, navigation, error messages, empty states, and shutdown. Try a simple workflow such as creating/opening a project and browsing server/service templates.

Stretch goal

In the Streamlit UI, create a new project and try adding:

• a virtual connector server
• a Multipass-backed Ubuntu server using the Docker backend

Stop if a step could alter or remove unrelated local infrastructure.

3. Contribute the result

Post a short report here or open a focused PR/bug issue:

OS + architecture:
Python / Docker / Task version:
Install lane:
Interface(s):
Commands or workflow tested:
Result: pass / partial / fail
First confusing step:
Error or relevant log excerpt:
Suggested fix:

A successful run is useful data. The best small contributions are corrected commands, clearer prerequisites, better error messages, screenshots, or a minimal reproduction for a bug.

Done when

• one install lane and one interface have been exercised on a clean setup
• cleanup succeeds where relevant
• the result is reported, and each discovered bug has reproducible steps