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

Gitea support #61

Open
jolheiser opened this issue Nov 15, 2022 · 4 comments · May be fixed by #99
Open

Gitea support #61

jolheiser opened this issue Nov 15, 2022 · 4 comments · May be fixed by #99

Comments

@jolheiser
Copy link

It would be neat to use this with releases on a Gitea instance as well.

@zyedidia
Copy link
Owner

Could you point me to an example of some software hosted on Gitea so I can see what might be involved?

@jolheiser
Copy link
Author

Sure! https://gitea.com/gitea/tea

Our API should be fairly similar to GH, so theoretically shouldn't be too much different aside from endpoints.

Of course, gitea is primarily for self hosting, so support would likely need to involve a way to specify some specific instance.

@jolheiser
Copy link
Author

I would also be willing to assist or even contribute this feature if you're okay with a proposal. 🙂

@zyedidia
Copy link
Owner

zyedidia commented Nov 15, 2022

Cool. It would be great to have Gitea support. I think it's unlikely I will implement it myself, but feel free to open a PR for it if you want. Maybe downloading from Gitea would require prefixing the repo with gitea.com. So it would be eget gitea.com/gitea/tea, for your example, or eget gitea.your.host/user/repo for custom hosted repos.

Hopefully it won't be too difficult to adapt the current code. You'll probably need to make a new GiteaAssetFinder in find.go, and then add some more parsing to getFinder in eget.go that will use the GiteaAssetFinder if it detects gitea in the hostname of the url, or something like that. Maybe if the custom host doesn't have gitea in the name, it would have to accept something like eget gitea/your.host/user/repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants