Set default log folder option
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
In general there are two options where Nextcloud stores logs. Either in the data directory or in the custom defined location for the log files (for the logs that have an option for this). Especially in bigger data directories the log files are somewhere between multiple user folders and/or the logs could be seperated in different locations.
Describe the solution you'd like
I would like a solution where i can set a default log folder in the config file. By this in the desired location a folder /logs with all logs inside would be created and makes it easier to get an overview of all logs withou the use of grep etc.
Describe alternatives you've considered
At the moment the only option to have everything in the same location is to delete custom paths for the normal logs so everything is stored atleast in the data directory.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the config file currently defines the data directory and custom log paths. Identify which log options should inherit a default /logs location, then verify behavior when custom paths remain. The issue names no files, tests, or entry points, so locating the affected configuration and coverage is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100