You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am looking for a HTTP server for Arch packages that works similar to chartmuseum. Since there is already a HTTP mirror for Arch packages with pacoloco I wanted to ask if it would be possible to extend it so that it is possible to upload packages via HTTP. My requirements would be:
HTTP API
update of the repository database
Multitanent capability
Delivery via container image
If there is already something I am quite interested in a solution.
The text was updated successfully, but these errors were encountered:
volker-raschek
changed the title
FR: Uploading package via HTTP
FR: Uploading packages via HTTP
Jan 23, 2022
Well, it would be quite a lot of work as you asked.
I wanted to ask if it would be possible to extend it so that it is possible to upload packages via HTTP. My requirements would be:
* HTTP API
Well, if you see the problem the other way around, it could be much easier. If you run a http(s) server with the packages and a db file (which is up to you on updating it as soon as you add a package), you can download them through pacoloco.
* update of the repository database
Otherwise, if you place the proper files locally where pacoloco does cache its packages, they will be served as is when they will be requested. It is pacman's job to check their signature.
* Multitenant capability
If you mean that pacoloco should be able to serve multiple clients at the same time, this is a WIP right now, there are some open issues about it
Hello,
I am looking for a HTTP server for Arch packages that works similar to chartmuseum. Since there is already a HTTP mirror for Arch packages with
pacoloco
I wanted to ask if it would be possible to extend it so that it is possible to upload packages via HTTP. My requirements would be:If there is already something I am quite interested in a solution.
The text was updated successfully, but these errors were encountered: