You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
var api = new ParseServer({
// logLevel:"error",
databaseURI: database.uri,
cloud: server.cloud,
appId: server.appId,
masterKey: server.masterKey,
serverURL: Config.server.serverURL,
directAccess: false,
maxLogFiles: 5
});
maxLogFiles not yet effective ????
I specified the maximum number of log files as 5, but the number of generated files still exceeds 5, I read the configuration of winston, it is necessary to use with maxsize, in the exceeding of maxsize will automatically delete the log files before 5. But I read the source code of winston and parse-server configurations, and this maxLogFiles configuration is not correct to be used in winston in the end.
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
maxLogFiles not yet effective ????
I specified the maximum number of log files as 5, but the number of generated files still exceeds 5, I read the configuration of winston, it is necessary to use with maxsize, in the exceeding of maxsize will automatically delete the log files before 5. But I read the source code of winston and parse-server configurations, and this maxLogFiles configuration is not correct to be used in winston in the end.
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
v6.3.1
windows
Database
MongoDB
5.0
Logs
The text was updated successfully, but these errors were encountered: