You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we're hardcoding the .coder suffix in the MenuItemView.
With coder/coder#16828 the HostnameSuffix will become a configurable value, thus we need to read that value and adjust the UI accordingly.
The text was updated successfully, but these errors were encountered:
I was wondering if we can instead use the same suffix as the CODER_ACCESS_URL. If CODER_WILDCARD_ACCESS_URL is set, we can reuse the wildcard cert for HTTPS apps. I am sure it will conflict with the configured DNS server resolving the CODER_ACCESS_URL and its subdomains.
Closes#93.
<img width="272" alt="image" src="https://github.com/user-attachments/assets/54786bea-9d32-432f-9869-5abd42a86516" />
The only time the hostname suffix is used by the desktop app is when an offline workspace needs to be shown in the list, where we naively append `.coder`. This PR sets this appended value to whatever `--workspace-hostname-suffix` is configured to deployment-side.
We read the config value from the deployment when:
- The app is launched, if the user is signed in.
- The user signs in.
- The VPN is started.
Currently we're hardcoding the
.coder
suffix in theMenuItemView
.With coder/coder#16828 the
HostnameSuffix
will become a configurable value, thus we need to read that value and adjust the UI accordingly.The text was updated successfully, but these errors were encountered: