Feature Request: Improve log accessibility and location for more consistent usage

[tamld]

Following up on previous observations while testing PrinterOne in more real-world usage, I wanted to share some additional feedback around how logs are handled.

Current behavior

• Log files are created in the same directory as the executable, with new files per session.
• While the application is running, some log files appear locked — which makes it hard to view or monitor them live.
• After a few sessions, this results in a growing number of log files in the same folder as the app.

Why this matters

From a user or admin perspective, this can become tricky when:

• The app is run continuously over days or weeks
• Users forget where the app was launched from
• There's a need to monitor logs across multiple sessions (especially during troubleshooting)

Suggestions (just for consideration)

• Use a central log folder (e.g. %LOCALAPPDATA%\PrinterOne\logs on Windows)
• Allow users to configure the log path in printer.json (optional)
• Consider having a unified log file in addition to session-specific ones, for longer-term continuity

No urgency at all — just sharing from usage.
Happy to discuss if this could fit the direction of the project. And if needed, I’m happy to help test it.

Thanks again for building something so practical!

[ashtray01]

Hello. Recently I've forked this repo and make some improvements check it out https://github.com/ashtray01/printerone
Also I have an logmrgr tool - it combines multiple logs into one file.