spkrepo
spkrepo copied to clipboard
Alternative package transfer
Current POST implementation to upload a package in system suffers multiple issues:
- slow, really slow
- if interrupted or failed because of conflict, still has to wait for another transfer to succeed
Proposal: a regular task watches folder for packages on system and process them with basic file move (and of course database insertions)
That way, it allows to use other file transfer tool like scp/rsync and also to retries insertion in case of conflict (after removal of conflictual package for instance)
But it would require direct "root" access to the FTP server, right?
I do not expect to use FTP server... If spkrepo code is granted access to a folder where ssh users may transfer packages, it should be OK and more secure than FTP. And there is only some accounts to create.
I think there is a way to make POST requests faster and this is the way to go. Not sure how anything can be done about that without some serious investigation though. Consistency is pretty hard wired in spkrepo so introducing a retry and we risk forgetting about that and eternal retry.