[GH-ISSUE #107] Clearing of logs #63

Closed
opened 2026-02-28 01:20:49 +03:00 by kerem · 2 comments
Owner

Originally created by @richard-underwood on GitHub (Aug 24, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/107

Hi - I need to make sure that logs can't be cleared too easily. I was thinking of implementing two new options (allowclearlogs allowrotatelogs) and then have a rotate logs button which would export the json to a file in a logs directory on the server. There could be a drop-down on the logs page to view rotated logs. Rotated log files could then be cleared up with standard logrotate (etc.) or backed up for compliance.

I'm happy to make the changes for this, but is this something which fits in with the roadmap, or would it conflict with other plans?

Originally created by @richard-underwood on GitHub (Aug 24, 2016). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/107 Hi - I need to make sure that logs can't be cleared too easily. I was thinking of implementing two new options (allowclearlogs allowrotatelogs) and then have a rotate logs button which would export the json to a file in a logs directory on the server. There could be a drop-down on the logs page to view rotated logs. Rotated log files could then be cleared up with standard logrotate (etc.) or backed up for compliance. I'm happy to make the changes for this, but is this something which fits in with the roadmap, or would it conflict with other plans?
kerem 2026-02-28 01:20:49 +03:00
Author
Owner

@tuxis-ie commented on GitHub (Aug 24, 2016):

Great idea!

Maybe directly implement a cron-like thingy? So a rotate could be automatically done upon a hit?

<!-- gh-comment-id:242016184 --> @tuxis-ie commented on GitHub (Aug 24, 2016): Great idea! Maybe directly implement a cron-like thingy? So a rotate could be automatically done upon a hit?
Author
Owner

@tuxis-ie commented on GitHub (Sep 13, 2016):

Merged!

<!-- gh-comment-id:246621984 --> @tuxis-ie commented on GitHub (Sep 13, 2016): Merged!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsedit#63
No description provided.