-
-
Notifications
You must be signed in to change notification settings - Fork 371
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
Allow separate gitea oauth URL #3513
Conversation
Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-3513.surge.sh |
IMO, this should also be named closes #3510 seems to be a drive-by fix that might better go in its own PR. |
This reverts commit 862980a.
I don't think so as it's not a dev flag. Maybe we can add some note in docs that most won't need it?
changed |
But for what real world scenario this is required? It just applies to dev/test setups, otherwise you have an accessible external domain anyway, or am I wrong? |
Hmm you're right, I just checked the issue again, will change it. |
If I didn't missed anything |
Yes me too, and I was wondering as well but had no time to check the details yet. |
I don't think so as |
Yes, you are right, the WOODPECKER_GITEA_URL needs to be accessible from the container and from the browser. If you can't find a value that fits both environments, this new option is required. Makes sense to me. |
Co-authored-by: Robert Kaussow <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3513 +/- ##
==========================================
- Coverage 36.08% 36.02% -0.06%
==========================================
Files 229 229
Lines 15489 15493 +4
==========================================
- Hits 5589 5582 -7
- Misses 9494 9504 +10
- Partials 406 407 +1 ☔ View full report in Codecov by Sentry. |
closes #3470