mirror of
https://github.com/warp-tech/warpgate.git
synced 2025-02-22 06:23:10 +08:00
Created HTTP targets on separate domains (markdown)
parent
e97dfe6f35
commit
d10d318976
1 changed files with 21 additions and 0 deletions
21
HTTP-targets-on-separate-domains.md
Normal file
21
HTTP-targets-on-separate-domains.md
Normal file
|
@ -0,0 +1,21 @@
|
|||
> This feature is available in v0.5+
|
||||
|
||||
Instead of using `?warpgate-target=` in the URL, you can use multiple domains/hostnames and link each to a specific target.
|
||||
|
||||
Accessing Warpgate over HTTP on a specific domain will then automatically select the corresponding target.
|
||||
|
||||
For optimal results, you want to host Warpgate on a common higher-level domain (e.g. `wg.acme.inc`, as set by the `external_host` config option), with target-specific domains as subdomains of this one (e.g. `gitlab.wg.acme.inc`) - this will prevent users from having to log in again when switching between domains (Warpgate will set its session cookie for all subdomains).
|
||||
|
||||
# Linking a target to a domain
|
||||
|
||||
Set the `http.external_host` property on the target config:
|
||||
|
||||
```diff
|
||||
- name: gitlab
|
||||
allow_roles:
|
||||
- "warpgate:admin"
|
||||
- qa
|
||||
http:
|
||||
url: http://10.0.0.2
|
||||
+ external_host: gitlab.wg.acme.inc
|
||||
```
|
Loading…
Reference in a new issue