-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Fetch Sponsors Automatically #80
Comments
Projectz will likely hit https://rawgit.com/bevry/sponsored/master/endpoints.json via that URL or via a cleaner redirect URL or via it as its own npm package (preferable) - as sponsored doesn't actually need to know the endpoints, only projectz, and as it may be useful to more than just projectz it should be it's own package/project. It may make sense where each org gets its own file, so we don't have to download/require everything... however that can come later I guess. If the scale actually does reach that large. Projectz will then hit the endpoint, and fetch in all sponsors with the |
pushed up a lot for this - https://github.com/bevry/sponsored got rid of the endpoints idea, instead projectz will go via a |
As we do not have enough backers to justify this, this now a PR / Bounty only request. |
this is now done with projectz v4: https://github.com/orgs/bevry/discussions/4 |
Closing #77 #16 #5 #4 in favour of this due to many APIs requiring tokens and thus requiring a custom endpoint.
Development of the endpoint has begun over at https://github.com/bevry/sponsored
The text was updated successfully, but these errors were encountered: