-
Notifications
You must be signed in to change notification settings - Fork 888
chore: add site
flag to buildinfo
#14868
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
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @ethanndickson and the rest of your teammates on |
site
flag to buildinfo
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, thanks for addressing this.
Side-note: coder/internal#54 (which you addressed in the previous PR) says to only open the browser on the first run. This happens on every run currently, and I think we ought to mention how to disable this.
Perhaps like this?
╔═══════════════════════════════════════════════╗
║ View the Web UI: ║
║ https://et23ntkhpueak.pit-1.try.coder.app ║
║ Disable auto-open with `--no-open` ║
╚═══════════════════════════════════════════════╝
Or only do so when the first user has not been created?
The database doesn't get initialised until a fair bit after we print the access URL, after which a bunch of logs will have streamed in. |
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, thanks 👍
03ac0f8
to
7fa8132
Compare
7fa8132
to
9075bf9
Compare
As of #14761, the access URL is automatically opened in the browser when running
coder server
. This becomes annoying when running versions of Coder without a frontend during development.This PR skips opening the URL in the browser when there is no frontend embedded into the binary. Since this is different from a
slim
build of Coder (i.e. a true slim build is ~40mb, this build is ~120mb), it wouldn't make sense to set the existingslim
flag to true. The solution is to add a newsite
flag, and ahasSite
function tobuildinfo
that can be used to detect frontendless builds.