-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit number of versions of a pad or delete them in Pad Settings #6194
Comments
To add on to this, it should be possible to disable the revisions feature entirely (at least for read only pads), either via a plugin or through etherpad settings. |
I absolutely need this feature too ... or at least "delete revisions older than 30 days" or alike. I used Etherpad (via Docker) for two months now. About hundred users. The postgresql database is zipped 400 MB now (!) This is insane.
Point 3 is actually the most helpful to save storage. Usage of my Etherpad: 611 MB / 971 pads = 0.63 MB per pad At least half of them are empty, so it's probably 1 - 2 MB per pad in average. And those pads contain only 100 lines of text. BTW, |
That is nice to see, however, admins do not want to manually spend 20 - 30 min a day to go through all pads... also considering data privacy/protection, this would not even be allowed. Again, we need:
Disabling revisioning is the most important one. |
Highly agree with this issue. With privacy laws being quite strict in Germany, our university's data privacy officer called out the fact that it's actually quite problematic that we dont regularly delete our pads. Currently, author names of pads are stored indefinitely since they are all over the revisions, and without a way to delete those, we now have to set all pads to self destruct after 2 years of not being changed (which is really annoying for the kinds of pads people keep revisiting for information but don't edit). Even if not automated, a simple solution to let us mass-delete revisions manually would help immensely. It might also speed up the process of getting the system up and running again after a shut down for maintenance. |
I played a little bit around how this could be achieved: |
That sounds great. I think that's a good idea. I don't know if it would be a plugin or core. Essentially anybody has the problem that revisions aren't deleted. |
Does that mean ALL author information or just the last active author? If it is just the last one, I think that might be fine enough (though does this method also get rid of all author colors?), so ultimately a really helpful solution. |
I think I need to clarify the storage of author information. Every author has a global ID with his color and a name and related pads:
This global ID (
Additional to the pad meta data the author is also referenced in the according revision:
This means that:
and this results in this behaviour:
|
Hmm, okay, that wouldnt quite fix the issue for us... Is it possible to auto-delete global author information (or neutralize, eg change name to "inactive author" or sth) after a certain amount of time has passed since their last assotiated contribution timestamp? Bc that in combination with the other proposed method would work out practically all issues we have. Or alternatively something that lets you auto-change the authors on any timestamp older than X to a global "dummy" author that is called "inactive author" or sth like that? |
I'll add an inactive author dummy variable. That should get rid of all the globalAuthors. |
I don't see the possibility of limiting the number of versions of a pad or cleaning up old versions.
The database grows without limit over time and exporting pads becomes long and heavy with numerous revisions .
Would it be possible to have this revision deletion option in Pad Settings?
Fred
The text was updated successfully, but these errors were encountered: