```shell
-$ dstack export create my-export --fleet my-fleet --importer team-b
- NAME FLEETS IMPORTERS
- my-export my-fleet team-b
+$ dstack export create my-export --fleet my-fleet --gateway my-gateway --importer team-b
+ NAME FLEETS GATEWAYS IMPORTERS
+ my-export my-fleet my-gateway team-b
```
-Both `--fleet` and `--importer` can be specified multiple times:
+`--fleet`, `--gateway`, and `--importer` can be specified multiple times:
```shell
$ dstack export create shared-gpus --fleet gpu-fleet-1 --fleet gpu-fleet-2 --importer team-b --importer team-c
- NAME FLEETS IMPORTERS
- shared-gpus gpu-fleet-1, gpu-fleet-2 team-b, team-c
+ NAME FLEETS GATEWAYS IMPORTERS
+ shared-gpus gpu-fleet-1, gpu-fleet-2 - team-b, team-c
```
@@ -62,9 +62,9 @@ Use `dstack export list` (or simply `dstack export`) to list all exports in the
```shell
$ dstack export list
- NAME FLEETS IMPORTERS
- my-export my-fleet team-b
- shared-gpus gpu-fleet-1, gpu-fleet-2 team-b, team-c
+ NAME FLEETS GATEWAYS IMPORTERS
+ my-export my-fleet my-gateway team-b
+ shared-gpus gpu-fleet-1, gpu-fleet-2 - team-b, team-c
```
@@ -72,27 +72,27 @@ $ dstack export list
### Update exports
-Use the `dstack export update` command to add or remove fleets and importers from an existing export:
+Use the `dstack export update` command to add or remove fleets, gateways, and importers from an existing export:
```shell
$ dstack export update my-export --add-fleet another-fleet --add-importer team-c
- NAME FLEETS IMPORTERS
- my-export my-fleet, another-fleet team-b, team-c
+ NAME FLEETS GATEWAYS IMPORTERS
+ my-export my-fleet, another-fleet my-gateway team-b, team-c
```
-To remove a fleet or importer:
+To remove a fleet, gateway, or importer:
```shell
$ dstack export update my-export --remove-importer team-b
- NAME FLEETS IMPORTERS
- my-export my-fleet, another-fleet team-c
+ NAME FLEETS GATEWAYS IMPORTERS
+ my-export my-fleet, another-fleet my-gateway team-c
```
@@ -114,7 +114,7 @@ Export my-export deleted
Use `-y` to skip the confirmation prompt.
-## Access imported fleets
+## Access imported resources
From the importer project's perspective, use `dstack import list` (or simply `dstack import`) to list all imports in the project — i.e., all exports from other projects that this project has been granted access to:
@@ -122,14 +122,14 @@ From the importer project's perspective, use `dstack import list` (or simply `ds
```shell
$ dstack import list
- NAME FLEETS
- team-a/my-export my-fleet, another-fleet
+ NAME FLEETS GATEWAYS
+ team-a/my-export my-fleet, another-fleet my-gateway
```
-Imported fleets also appear in `dstack fleet list` in the `
/` format:
+Imported fleets and gateways also appear in `dstack fleet list` and `dstack gateway list` in the `/` format:
@@ -140,17 +140,24 @@ $ dstack fleet list
team-a/my-fleet 2 A100:80GB:8 - ssh - active 1 week ago
team-a/another-fleet 1 H100:80GB:4 - ssh - active 2 days ago
+$ dstack gateway list
+ NAME BACKEND HOSTNAME DOMAIN DEFAULT STATUS
+ team-a/my-gateway aws (eu-west-1) 10.0.0.4 gtw.mycompany.example running
+
```
-Imported fleets can be used for runs just like the project's own fleets.
+Imported resources can be used for runs just like the project's own resources.
```yaml
-type: dev-environment
-ide: vscode
+type: service
+image: nginx
+port: 80
+
+gateway: team-a/my-gateway
fleets:
- my-local-fleet
@@ -166,4 +173,5 @@ fleets:
1. Check the [`dstack export` CLI reference](../reference/cli/dstack/export.md)
1. Check the [`dstack import` CLI reference](../reference/cli/dstack/import.md)
1. Learn how to manage [fleets](fleets.md)
+ 1. Learn how to manage [gateways](gateways.md)
1. Read about [projects](projects.md) and project roles
diff --git a/mkdocs/docs/concepts/gateways.md b/mkdocs/docs/concepts/gateways.md
index 5e072a696..bd7118796 100644
--- a/mkdocs/docs/concepts/gateways.md
+++ b/mkdocs/docs/concepts/gateways.md
@@ -57,6 +57,17 @@ A gateway requires a `domain` to be specified in the configuration before creati
Once the gateway is created and assigned a hostname, configure your DNS by adding a wildcard record for `*.` (e.g. `*.example.com`). The record should point to the gateway's hostname and should be of type `A` if the hostname is an IP address (most cases), or of type `CNAME` if the hostname is another domain (some private gateways and Kubernetes).
+??? info "Project name interpolation"
+ You can use the `${{ run.project_name }}` variable to include the service’s project name in the domain name. This is especially useful when [exporting](exports.md) the gateway to multiple projects, as it ensures each importer receives a unique domain name.
+
+ ```yaml
+ type: gateway
+ name: global-gateway
+ backend: aws
+ region: eu-west-1
+ domain: ${{ run.project_name }}.mycompany.example
+ ```
+
### Backend
You can create gateways with the `aws`, `azure`, `gcp`, or `kubernetes` backends, but that does not limit where services run. A gateway can use one backend while services run on any other backend supported by dstack, including backends where gateways themselves cannot be created.
@@ -174,6 +185,11 @@ domain: example.com
!!! info "Reference"
For all gateway configuration options, refer to the [reference](../reference/dstack.yml/gateway.md).
+## Export gateways
+
+Gateways can be exported to other projects, allowing those projects to use the exported gateways
+for running services. See [Exports](exports.md) for more details.
+
## Manage gateways
### List gateways
diff --git a/src/dstack/_internal/core/models/gateways.py b/src/dstack/_internal/core/models/gateways.py
index ce28c6205..6f92b449b 100644
--- a/src/dstack/_internal/core/models/gateways.py
+++ b/src/dstack/_internal/core/models/gateways.py
@@ -72,7 +72,15 @@ class GatewayConfiguration(CoreModel):
),
] = None
domain: Annotated[
- Optional[str], Field(description="The gateway domain, e.g. `example.com`")
+ Optional[str],
+ Field(
+ description=(
+ "The gateway wildcard domain name, e.g. `example.com`."
+ " Service domain names are constructed as `.