> It is unlikely that a blog engine will be able to generate an apt
> repository. Could you say more about the restriction?
Basically I'm restricted due to git version control service providers.
I managed to turn the Hugo content generator to host deb packages
(e.g. link to download) and mimic json reply.
The next challenge is to comply towards Apt protocol so that
user can do "apt update && apt upgrade" instead of downloading
the deb manually.
If the exploration is fruitful, we can remove a lot of CI dependencies.
It's more for preventive measure for ghosting supplier.
Regards,
Holloway