runbot/forwardport/data
Xavier Morel 029957dbeb [IMP] *: trigger-ify task queue type crons
These are pretty simple to convert as they are straightforward: an
item is added  to a work queue (table), then a cron regularly scans
through the table executing the items and deleting them.

That means the cron trigger can just be added on `create` and things
should work out fine.

There's just two wrinkles in the port_forward cron:

- It can be requeued in the future, so needs a conditional trigger-ing
  in `write`.
- It is disabled during freeze (maybe something to change), as a
  result triggers don't enqueue at all, so we need to immediately
  trigger after freeze to force the cron re-enabling it.
2024-08-02 15:14:50 +02:00
..
crons.xml [IMP] *: trigger-ify task queue type crons 2024-08-02 15:14:50 +02:00
queues.xml [IMP] mergebot, forwardbot: various UI bits 2022-06-30 15:07:49 +02:00
security.xml [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +02:00
views.xml [FIX] forwardport: count next to users should be the fwport 2024-06-28 08:18:34 +02:00