Tox Development Environtmnet Criteria #385

Closed
opened 2026-03-19 04:43:28 +00:00 by Rockachopa · 0 comments
Owner

When I run tox -e dev I expect:
Completely isolated workspace and docker compose deploy
Gracefully selecting another port if its taken
Clickable link to open the daskboard in the web app
clickable links to all other WEBGUI that are part of the tool that may be exposed
A status line (Backend Inference Source, Timmy Release version/ Git commit timestamp, smoke tests)
Also dropped into a shell environment so when I the the timmy cli command, it points specifically and only to my dev timmy.
And everything updates on code change and is running as close to runtime from the files on disk as possible.

Please update and test the tox -e dev pipeline to make sure all these criteria are satisfied where reasonable with room for reasonable pushback or liberties for better more elegant solutions to the same effect.

When I run tox -e dev I expect: Completely isolated workspace and docker compose deploy Gracefully selecting another port if its taken Clickable link to open the daskboard in the web app clickable links to all other WEBGUI that are part of the tool that may be exposed A status line (Backend Inference Source, Timmy Release version/ Git commit timestamp, smoke tests) Also dropped into a shell environment so when I the the `timmy` cli command, it points specifically and only to my dev timmy. And everything updates on code change and is running as close to runtime from the files on disk as possible. Please update and test the tox -e dev pipeline to make sure all these criteria are satisfied where reasonable with room for reasonable pushback or liberties for better more elegant solutions to the same effect.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#385