It appears as though Explo isn't writing to STDOUT when jobs are running. I have to log into the (nice job btw!) WebUI to see the log status. I use Dozzle, Dockhand, and other applications to check on container status, and Explo doesn't write anything (AFAIK) to the standard STDOUT or STDERR except for initial startup like WebUI and cron registration. And maybe logins. I'd love to be able to see actual running progress here.
[setup] Starting web UI...
[setup] Web UI available at http://localhost:7288
[setup] Initializing cron jobs...
time=2026-06-13T06:57:00.439-04:00
level=INFO
msg=Starting Explo...
[setup] Registered job: WEEKLY_JAMS
Schedule: 30 00 * * 1
Command : ./explo --playlist weekly-jams
[setup] Registered job: WEEKLY_EXPLORATION
Schedule: 15 00 * * 2
Command : ./explo --playlist weekly-exploration
[setup] Starting cron...
time=2026-06-13T06:57:00.530-04:00
level=INFO
msg=Explo web UI started
addr=:7288
time=2026-06-13T06:57:16.189-04:00
level=ERROR
msg=session not found
time=2026-06-13T06:57:18.263-04:00
level=INFO
msg=successful login
user=admin
It appears as though Explo isn't writing to STDOUT when jobs are running. I have to log into the (nice job btw!) WebUI to see the log status. I use Dozzle, Dockhand, and other applications to check on container status, and Explo doesn't write anything (AFAIK) to the standard STDOUT or STDERR except for initial startup like WebUI and cron registration. And maybe logins. I'd love to be able to see actual running progress here.