Support multiple external URLs
This issue (probably needs to be converted into epic) is about changing GitLab to support multiple external URLs.
Things that needs to changed:
- Stable link generation
- CORS (example: omnibus-gitlab#5425 (comment 1448056007))
- Possibly others!
Original Description
I maintain a GitLab instance for my employer. The external URL is configured to gitlab.MyFullCompanyName.local
, to ensure as much compatibility as possible. However, for day to day use, this is obnoxiously long and is generally elided to http://gitlab, or it's alias, http://git. I am happy that the FQDN is used for cloning URLs as this means remote URLs will almost always work (some machines don't have MyFullCompanyName.local
in the DNS search suffixes and thus can't resolve the non-FQDN). But for access via the front-end, this discrepancy can cause issues, namely with links. Relative links and absolute links that start with /
work, but truly absolute links that start with http://gitlab.MyFullCompanyName.local/
are frustrating, as they send you to a different DN and require another login.
Original Proposal
What I propose depends on how the GitLab team views secondary external URLs:
-
If GitLab should work from any external URL from which it is accessible
- Then I raise the issue that some links use the FQDN. The one that gets me is the project dropdown from the left-hand menu. When I search for a project, the link to that project uses the FQDN.
-
If GitLab should only be accessed from the configured external URL
- Then I request a setting to allow it to be accessed from any external URL
- Or I request a whitelist of multiple external URLs from which gitlab can be accessed.
Either way, I want this change to only apply to HTML links. I like the configured FQDN being used for cloning URLs and the registry.