Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Gitea Package Registries (e.g. for Debian, RPM, Alpine,...) #4068

Open
2 of 3 tasks
CMiksche opened this issue Jun 3, 2023 · 4 comments
Open
2 of 3 tasks
Assignees
Labels
enhancement New feature or request good-first-issue
Milestone

Comments

@CMiksche
Copy link

CMiksche commented Jun 3, 2023

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:

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

(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

  • I did search for other open and closed issues before opening this

Supporter

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

No response

@CMiksche CMiksche added enhancement New feature or request triage Issue pending triage by one of the maintainers labels Jun 3, 2023
@caarlos0
Copy link
Member

caarlos0 commented Jun 6, 2023

interesting! seems very doable, just don't have the bandwidth for this release, will try it for the next one.

contributions also welcome :)

@caarlos0 caarlos0 removed the triage Issue pending triage by one of the maintainers label Jun 6, 2023
@caarlos0 caarlos0 added this to the v1.20.0 milestone Jun 6, 2023
@tashian
Copy link
Contributor

tashian commented Aug 9, 2023

We've had a lot of folks asking us for proper package repos and this could be a good approach!
+1

@caarlos0 caarlos0 modified the milestones: v1.20.0, v1.21.0 Aug 12, 2023
@caarlos0 caarlos0 modified the milestones: v1.21.0, v1.22.0 Sep 23, 2023
@caarlos0 caarlos0 modified the milestones: v1.22.0, v1.23.0 Nov 7, 2023
@caarlos0 caarlos0 modified the milestones: v1.23.0, v1.24.0 Dec 29, 2023
@caarlos0 caarlos0 modified the milestones: v1.24.0, v1.25.0 Feb 7, 2024
@lng2020
Copy link

lng2020 commented Mar 3, 2024

I think gitea/go-sdk should support the uploading package sdk first, otherwise, there is no way for goreleaser to support this feature. Please let me know if I'm missing something or if there is another workaround.

@caarlos0
Copy link
Member

caarlos0 commented Mar 3, 2024

maybe @jolheiser have more info?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good-first-issue
Projects
None yet
Development

No branches or pull requests

4 participants