Cleverer 'update' mechanism

Bug #620394 reported by Daniel Holbach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Fix Released
Medium
Daniel Holbach

Bug Description

The LoCo Directory gets more and more functions and more and more external data find its way into the LD. We don't need to udpate all the data in every cron run.

 - update-countries: once a day (even less would be fine)
 - update-languages: once a day (even less would be fine)
 - lpupdate:
   + get list of teams (every 10-15 minutes?)
   + get list of admins/owners (every 10-15 minutes?)
   + get statistics (bug 605651) (every 2 hours?)
   + get all team members (so we can appoint loco contacts) (every 30 minutes?)
 - etc. - there will be even more stuff in the future.

To make sure we don't have too many concurrent cronjob going on, I suggest we kick off "./manage.py update" every 10 minutes. It itself should keep track of which job needs to be run in which intervals and let the jobs leave stamp files somewhere, so we can check when it was last run.

Tags: data

Related branches

Changed in loco-directory:
importance: Undecided → Medium
status: New → Triaged
tags: added: data
Changed in loco-directory:
assignee: nobody → Daniel Holbach (dholbach)
Changed in loco-directory:
status: Triaged → In Progress
Changed in loco-directory:
milestone: none → 0.2.18
status: In Progress → Fix Committed
Changed in loco-directory:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.