[17:49:22]
<Maranda[x]> You can't Metronome only supports TCP sockets the only way would be having caddy listening on a different port and reverse proxying without SNI or listening on loopback (127.0.0.1) if on same machine without encryption
[21:57:47]
<sarvo> Managed to make it work. Here is the code so you can review it:
https://codeberg.org/Nimble/metronome-filer/src/branch/delete
Now I am off to test the autodelete. However there is something that is still bothering me, the delete_url, everytime it changes metronome "forgets it" meaning that in all the changing and uploads I sent to the same server with the same url, the delete only recognizes the delete_url.
What I mean is that I have files now that will never get deleted, even tho the upload url is the same for all of them because it doesn't match with the latest delete_url
[22:11:57]
<Maranda> > <sarvo> Managed to make it work. Here is the code so you can review it:
>
> https://codeberg.org/Nimble/metronome-filer/src/branch/delete
>
> Now I am off to test the autodelete. However there is something that is still bothering me, the delete_url, everytime it changes metronome "forgets it" meaning that in all the changing and uploads I sent to the same server with the same url, the delete only recognizes the delete_url.
>
> What I mean is that I have files now that will never get deleted, even tho the upload url is the same for all of them because it doesn't match with the latest delete_url
Metronome stores the delete slots with the URLs if you change the deletion URL base that will invalidate all stored slots obviously