[Feature Request] Database/Log retention period to limit database size, and an offline/read only mode #873

Closed
opened 2026-04-05 16:31:08 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @i0ntempest on 4/19/2024

Since my original request is too excessive and requires an almost complete rewrite of VRCX (as others commented below), I updated my request to make it simpler.
Explain in detail what your suggested feature would be used for.
Allow users to set a log retention period, and automatically delete logs older than that period.
And an offline/read only mode allowing users to open a database to examine data without making changes.

Describe how it would look if it requires a UI.
A few new options:

  • A toggle to enable retention period
  • Length of the retention period

Explain why people would want to use it.
With the default database location being in %appdata%, this would avoid filling up users' C drive. Users may implement periodical backups with backup software or custom script, and the offline mode would allow the user to go back and examine backups.

Original issue:
Explain in detail what your suggested feature would be used for.
I think a lot of people have VRCX running all the time to log stuff, and the database file could get rather big. I am planning to run it on my home server, so in addition to features requested here, I'd like to request another useful feature that is log rotation.
Basically this feature would automatically archive data (with optional compression) that is older than customizable time (say 3 months) from database (maybe with sensitive stuff like passwords removed) to some customizable directory, every some customizable length (say a month), and then remove archived data from the main database. And then, a read only mode mentioned in then issue above, in addition to be able to open another main database at some network location, could also be used to open an archive database without modifying it.

Describe how it would look if it requires a UI.
A few new options:

  • Toggle to enable rotation
  • How old is the data to be archived
  • How frequently to archive process
  • Location of archives (a folder)
  • (Optional toggle to enable compression of archives)
*Originally created by @i0ntempest on 4/19/2024* Since my original request is too excessive and requires an almost complete rewrite of VRCX (as others commented below), I updated my request to make it simpler. **Explain in detail what your suggested feature would be used for.** Allow users to set a log retention period, and automatically delete logs older than that period. And an offline/read only mode allowing users to open a database to examine data without making changes. **Describe how it would look if it requires a UI.** A few new options: - A toggle to enable retention period - Length of the retention period **Explain why people would want to use it.** With the default database location being in %appdata%, this would avoid filling up users' C drive. Users may implement periodical backups with backup software or custom script, and the offline mode would allow the user to go back and examine backups. **Original issue:** **Explain in detail what your suggested feature would be used for.** I think a lot of people have VRCX running all the time to log stuff, and the database file could get rather big. I am planning to run it on my home server, so in addition to features requested [here](https://github.com/vrcx-team/VRCX/issues/748), I'd like to request another useful feature that is log rotation. Basically this feature would automatically archive data (with optional compression) that is older than customizable time (say 3 months) from database (maybe with sensitive stuff like passwords removed) to some customizable directory, every some customizable length (say a month), and then remove archived data from the main database. And then, a read only mode mentioned in then issue above, in addition to be able to open another main database at some network location, could also be used to open an archive database without modifying it. **Describe how it would look if it requires a UI.** A few new options: - Toggle to enable rotation - How old is the data to be archived - How frequently to archive process - Location of archives (a folder) - (Optional toggle to enable compression of archives)
MrUnknownDE added the NicheFeatureNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheNicheFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeatureFeature labels 2026-04-05 16:31:13 +02:00
Sign in to join this conversation.
No Label Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche Niche
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/VRCX#873