fix(logging): 馃悰 Use script-relative log path instead of CWD-relative - #333
Merged
Conversation
DouglasHalse
force-pushed
the
fix/cron-log-path
branch
from
June 7, 2026 20:22
abe6e5b to
b844b4b
Compare
DouglasHalse
force-pushed
the
fix/cron-log-path
branch
from
June 7, 2026 20:22
b844b4b to
be63469
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When launched by cron, the working directory is typically
$HOME, so the old relative"logs"path landed in/home/pi/logs/instead of the project'slogs/directory.Fix: derive
LOG_DIRfromlogger.py's location on disk so it always resolves inside the project root, regardless of how the app is launched.