You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2015/10/22 21:31:41 UTC
[allura:tickets] #8009 Set up maintenance command to clean 'notification'
collection
---
** [tickets:#8009] Set up maintenance command to clean 'notification' collection**
**Status:** open
**Milestone:** unreleased
**Labels:** docs
**Created:** Thu Oct 22, 2015 07:31 PM UTC by Dave Brondsema
**Last Updated:** Thu Oct 22, 2015 07:31 PM UTC
**Owner:** nobody
The records in the `notification` collection do not need to stick around forever. It'd be good to have a paster command to clean up old ones, and documentation about setting up a cron job for it. Even better if we can think of a smart way to handle it automatically within allura, so a cron job wouldn't be necessary. Here's the basic query:
db.notification.remove({pubdate:{$lt: new Date(Date.now() - 1000*60*60*24*31*2)}})
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.