[20:49:13]
<Testchatter> Testing, 123...
[21:41:25]
<massimilian0> > Testing, 123...
Test success?
[23:37:44]
<sarvo> > Maranda:
> 2023-01-10 02:49 (CST)
> If you think there's room for improvement feel free to submit a PR
Could do it but maybe later my free time is coming to an end and somehow I understand go more than lua but I may read through the code at some point
[23:38:47]
<sarvo> > Maranda:
> 2023-01-10 02:44 (CST)
> sarvo: no because depending on the storage used Metronome is mostly agnostic of the users' and can't list 'em. And some data gets loaded only on demand perhaps having to traverse all user store to rectify the URLs is a real pita. Also think of when you just change upstream http file server keeping the old for a while before decommissioning until it's drained
I have to ask, how could I flush all the previous entries of a server URL that is no longer used in metronome?
[23:45:09]
<Maranda> sarvo: what's the storage backend you're using, flat files?
[23:45:24]
<sarvo> sql + postgresql
[23:45:43]
<Maranda> Huhu
[23:45:53]
<Maranda> with Metronome?
[23:49:11]
<Maranda> sarvo: unfortunately I don't exactly recall the structure of the SQL storage atm, with flat files all it would be just purging /var/lib/metronome/<host>/http_upload_external
[23:51:26]
<Maranda> so given the key-value store mapping in SQL is...
[23:51:34]
<Maranda>
```
Metronome - key-value, map
| host | user | store | key | type | value |
```
[23:54:52]
<Maranda> ``DELETE FROM `metronome` WHERE `host`=<insert host> AND `user`=<user> AND `store`='http_upload_external';`` iterating users from the "accounts" store
[23:57:00]
<Maranda> or something, have a double check, going on memory here