Support Gitea Package Registries (e.g. for Debian, RPM, Alpine,...) #5610
Replies: 8 comments 1 reply
-
|
interesting! seems very doable, just don't have the bandwidth for this release, will try it for the next one. contributions also welcome :) |
Beta Was this translation helpful? Give feedback.
-
|
We've had a lot of folks asking us for proper package repos and this could be a good approach! |
Beta Was this translation helpful? Give feedback.
-
|
I think |
Beta Was this translation helpful? Give feedback.
-
|
maybe @jolheiser have more info? |
Beta Was this translation helpful? Give feedback.
-
I don't think this need Gitea's support except generic packages. all other packages have their own official tools to upload/download packages. |
Beta Was this translation helpful? Give feedback.
-
|
@lng2020 You can use their HTTP API: curl --user your_username:your_password_or_token \
--upload-file path/to/file.deb \
https://gitea.example.com/api/packages/testuser/debian/pool/bionic/main/upload |
Beta Was this translation helpful? Give feedback.
-
|
PS: gonna convert this into a discussion until its better defined. |
Beta Was this translation helpful? Give feedback.
-
|
is this something people are still interested in? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
While using Gitea, packages and binaries are currently just being uploaded as assets to releases.
But Gitea now provides its own package registries. In the current development version, there is e.g. a registry for Debian, RPM, Alpine and many others.
Instead of uploading it as a Asset, we could upload it directly to the Gitea Package Registry which would make distribution for the users easier.
In my use case, I have multiple packages which I want to distribute to multiple servers via the Gitea Package Registry. I can already do that but would need to write my own code for adding it to the Gitea Registry.
Describe the solution you'd like
We already have the Gitea Token, Repository and Organisation or User as Env Vars in this project, for supporting the Gitea Package registry, just a few more API calls would have to be added.
E.g. to publish a package:
(See: https://docs.gitea.com/next/usage/packages/packages/debian)
Describe alternatives you've considered
The current alternative would be that every user creates his own implementation. My plan would be to make the API-Call myself in the Pipeline and upload the package there.
Search
Supporter
Code of Conduct
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions