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
Copy file name to clipboardExpand all lines: docs/concepts/services.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,20 +4,37 @@ description: Defang allows you deploy services, defined as containers, to the cl
4
4
sidebar_position: 200
5
5
---
6
6
7
-
# Services
7
+
import Tabs from '@theme/Tabs';
8
+
import TabItem from '@theme/TabItem';
8
9
9
-
Defang allows you deploy services defined as containers. You can define your services using a [Compose file](./compose.md) or a [Pulumi program](./pulumi.md). Services can be exposed to the internet or kept private, and can communicate between themselves using the following conventions for hostnames:
10
+
# Services
10
11
11
-
`<username>-<service-name>`
12
+
Defang allows you deploy services defined as containers. You can define your services using a [Compose file](./compose.md) or a [Pulumi program](./pulumi.md). Services can be exposed to the internet or kept private, and can communicate between themselves using certain conventions for hostnames.
12
13
13
14
### Service Name Resolution
14
-
As shown above, Defang identifies services by the [account username](./accounts.md) and the service name.
15
+
16
+
Defang identifies services by using your [account username](/docs/concepts/accounts), [project name](/docs/concepts/projects), and service name. The port is included in the [domain](/docs/concepts/domains) for the service.
17
+
15
18
16
19
:::tip
17
-
Service names are defined in your Compose file or your Pulumi program.
20
+
Service names are defined in your Compose file or in your Pulumi program.
18
21
:::
19
22
20
-
This means that if you have multiple Defang projects with the same service name, they will conflict with each other. To avoid naming conflicts, we recommend using a different name for each service you define.
0 commit comments