M3 §4/7: the log-tailing command produces no output

From beta feedback by @yard-mschwartz (2026-08-10 batch).

This commando doesn't work for me, because there is no log: tail -f workspace/server/data/nextcloud.log | python3 -m json.tool. I did set debug mode and log level correctly.

PHP Track > M3 Backend Fundamentals > Section 4/7, Exercise.

He reports having set debug mode and log level as instructed, so this is very likely ours, not his setup. Things to check when picking this up:

• Whether the log path is right for the nextcloud-docker-dev layout the course uses — the file may not be at workspace/server/data/nextcloud.log at all, or may not exist until something has actually been logged.
• Whether | python3 -m json.tool is even correct: it expects one complete JSON document on stdin, while nextcloud.log is newline-delimited JSON, one object per line. Piping a tail -f stream into it will not pretty-print line by line the way the text implies.
• Whether the exercise should instead point at occ log:tail/occ log:watch, which avoids the path question entirely.

Fix should include a real, verified command and a note on what to do when the file is empty (i.e. trigger a request first).

Locate the M3 Backend Fundamentals Section 4/7 exercise text and reproduce the command in the nextcloud-docker-dev layout. Verify the log location and newline-delimited format, trigger a request when the file is empty, and document a command that produces readable entries with the required empty-file guidance.