[GH-ISSUE #53] [Feature Request]: Ability to limit log files #42

New issue

Closed

opened 2026-03-23 20:35:16 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:35:16 +00:00

Owner

Originally created by @p-rintz on GitHub (Jun 10, 2025).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/53

I've read the documentation

I have read the how to open an issue guide, particularly the feature request section.

Your Feature Request

I recently installed the plugin and enabled sync to my tubearchivist instance.
The plugin is logging a massive amount of text to the syslog and generated rougly 40Gb of data over a few days.

Describe the solution you'd like

Ability to limit the amount of logging somehow.

Additional context

Your help is needed!

Yes I will work on this in the next few days or weeks.

Originally created by @p-rintz on GitHub (Jun 10, 2025). Original GitHub issue: https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/53 ### I've read the documentation - [x] I have read the [how to open an issue](https://github.com/tubearchivist/tubearchivist/blob/master/CONTRIBUTING.md#how-to-open-an-issue) guide, particularly the [feature request](https://github.com/tubearchivist/tubearchivist/blob/master/CONTRIBUTING.md#feature-request) section. ### Your Feature Request ## Is your feature request related to a problem? Please describe. I recently installed the plugin and enabled sync to my tubearchivist instance. The plugin is logging a massive amount of text to the syslog and generated rougly 40Gb of data over a few days. ## Describe the solution you'd like Ability to limit the amount of logging somehow. ## Additional context ### Your help is needed! - [ ] Yes I will work on this in the next few days or weeks.

mirror closed this issue

2026-03-23 20:35:16 +00:00

mirror commented

2026-03-23 20:35:17 +00:00

Author

Owner

@DarkFighterLuke commented on GitHub (Jul 10, 2025):

Hi, you are absolutely right and i was about to do this for the next release, but i see that #57 already addresses this issue, i will merge it soon, thanks to @Atinoda.

@DarkFighterLuke commented on GitHub (Jul 10, 2025): Hi, you are absolutely right and i was about to do this for the next release, but i see that #57 already addresses this issue, i will merge it soon, thanks to @Atinoda.