Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Prune activity log

#48

The activity log can grow very quickly and it would be helpful to be able to prune it either manually or through an automatic setting without having to manually manipulate the database tables.

Reported by labman · October 7th, 2008 @ 09:58 AM

State: resolved
Milestone: 5.0.3
Assigned to: Charles Brunet Charles Brunet

Activity

  1. lux
    lux

    Also scheduler log file and versioning tables. For the latter, it would need a setting that says:

    Versions to keep? All, 1, 2, 5, 10, 20

    Or something to that effect. These would best be implemented through the scheduler I would think.

    January 4th, 2009 @ 02:57 PM

  2. Charles Brunet
    Charles Brunet
    • Assigned user changed from lux to Charles Brunet
    • State changed from new to open
    • Tag changed from activity, feature, log to activity, feature, history, log, scheduler, version

    Done for activity log and for versionning history.

    Scheduler log is still to do.

    July 29th, 2009 @ 04:20 PM

  3. Charles Brunet
    Charles Brunet
    • State changed from open to resolved

    implemented logrotate scheduler task to rotate scheduler logs.

    August 4th, 2009 @ 04:22 PM

  4. Charles Brunet
    Charles Brunet
    • Milestone set to 5.0.3

    [milestone:id#47011 bulk edit command]

    August 7th, 2009 @ 09:41 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.