-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Locally Self hosted Docker returns internal error #4862
Comments
Hi! Shields emits stack traces for the errors to standard output, so you should be able to get more details in the container. |
Hi this is what it reprots
|
here a more complete version just in case
so it looks i must be missing something? |
To use the GitHub badges, you need to set a GitHub token: https://github.com/badges/shields/blob/master/doc/server-secrets.md#github In theory you should be able to generate 60 badges/hr without a token, however this isn't possible because of #2754. |
Are you able to get any of the other, non-GitHub badges, to work? |
excellent it now works on Azure with minimum efforts, I only added a I have another question, my needs are to support my Os project and I have shields public on Azure is there some setting that will allow only my Os organization repos to access it? |
No, there is nothing like this today. If you want to limit access, you'd probably have to host it inside your firewall. |
You could also potentially restrict access to your self-hosted Shields instance leveraging Azure features (depending on which services you're leveraging) |
Should provide better debuggability in self-hosting cases like #4862 but also on the production server.
I started the Docker container locally as per docks and the site runs fine. However none of the badges are created. Is there some component i miss? Are there any instructions to debug it?
The text was updated successfully, but these errors were encountered: