-
Notifications
You must be signed in to change notification settings - Fork 887
chore: Deploy internally accessible godoc container #1415
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
Conversation
is there a preview URL? 👀 |
Codecov Report
@@ Coverage Diff @@
## main #1415 +/- ##
==========================================
- Coverage 67.19% 67.14% -0.06%
==========================================
Files 287 287
Lines 19307 19307
Branches 241 241
==========================================
- Hits 12974 12964 -10
- Misses 4998 5006 +8
- Partials 1335 1337 +2
Continue to review full report at Codecov.
|
Sort of: https://internal-docs-c2oq3ixdcq-uc.a.run.app/pkg/github.com/coder/coder/ Unfortunately it's a bit clumsy to access at the moment. Based on the discussion in #1398 I haven't yet made the endpoint publicly accessible, so you have to pass a bearer token as described here. I used the ModHeader Chrome extension to test it out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Build a container image that runs
godoc
on our source code, and deploy it to Cloud Run for internal use.The Cloud Run/Build configurations are currently manually configured, but the important settings are:
/scripts/internal-docs/cloudbuild.yaml
gcr.io/coder-devrel/internal-docs
The container uses https://github.com/dwahler/go-tools, which is a fork of golang.org/x/tools that doesn't serve traffic until it's finished scanning the repository, which is necessary to play nicely with Cloud Run's traffic balancing.
Fixes #1398