Control logging output location

[jnsgruk]

Presently, homepage outputs its logs both to stdout and to a file by default.

If homepage is run on Kubernetes, or under another service manager which can collect/rotate logs then you end up with duplication.

It would be useful to be able to disable the file logging for these cases, and rely only on logs at stdout, and on the other means for collecting/rotating logs.

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To disable file logging and rely solely on stdout for logs in Homepage, you can try setting the logpath to /dev/null in the settings.yaml file. This should redirect the logs to a null device, effectively discarding them. However, please note that this method is not explicitly documented in the Homepage documentation, and its effectiveness may depend on how the application handles file paths for logging.

Here's an example of what the settings.yaml might look like with the logpath set to /dev/null:

logpath: /dev/null

Before making this change, ensure to back up your configuration and test the changes in a safe environment to verify that it does not affect the application's functionality.

If this method does not work or if you prefer a more standard approach, you may need to reach out to the Homepage support community or check the documentation for more specific instructions on managing log output.

Remember that disabling file logging may make it more difficult to troubleshoot issues in the future, as you will not have a persistent log file to review.

This comment was generated by Glime.

[jnsgruk]

For reference this won't work at the log handler in homepage creates a directory at the given path, so using /dev/null or /dev/log won't work 😊

[shamoon]

Ha, good to know we're still smarter than the bots, for now...

Got my vote, thanks for opening a FR.

[jnsgruk]

Proposed implementation: jnsgruk@3be28a2

#3075

[shamoon]

#3075

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.