Added supported Compose spec properties

docs/concepts/compose.md

@@ -6,35 +6,247 @@ sidebar_position: 150
 
 # Compose
 
-You might be familiar with `docker-compose.yml` files, now known as the [Compose specification](https://docs.docker.com/compose/compose-file/) and `compose.yaml` files. It's a simple way to define and run multi-container Docker applications. Defang allows you to use `compose.yaml` files to deploy your application to the cloud.
+Defang allows you to use `compose.yaml` files to deploy your application to the cloud. 
+The `compose.yaml` file is a simple way to define and run multi-container applications. 
+This file format may look familiar to you if you've used [Docker](https://docker.com).
 
-## How it works
+The [Compose Specification](https://github.com/compose-spec/compose-spec/blob/main/spec.md#compose-file) lets you define a platform-agnostic application designed as a set of containers which are configured to run together with shared resources. These applications may be destined for any [OCI](https://opencontainers.org/) Container Runtime. Defang does the heavy lifting to deploy to your favourite cloud platform using this file.
 
-You can define your [services](./services.md) using a `compose.yaml` file in the root of your project, or use the [`defang generate` command](../tutorials/generate-new-code-using-ai.mdx) to generate one (along with other resources). This file is used to define your application's services and how they run. You can edit this file to add more services or change the configuration of existing services.
+## How It Works
+
+You can create a `compose.yaml` file in the root of your project, or use the [`defang generate`](../tutorials/generate-new-code-using-ai.mdx) command to create one for you (along with other resources). This file is used to define your application's [services](./services.md) and how they run. You can edit this file to add more services or change the configuration of services.
 
 When you run `defang compose up`, Defang will read your `compose.yaml` file and [deploy](./deployments.md) the services named in that file to the cloud.
 
-## Service Name Resolution
+## Example of a Compose File
+Here is a basic `compose.yaml` file that contains all the required properties for deployment in Defang. 
+
+```yaml
+services:
+  service-example:
+    image: nginx:latest # use one of: image (shown on this line) or build (shown below)
+    # build: 
+    #   context: .
+    #   dockerfile: Dockerfile
+  ports: 
+    - mode: ingress # specify ports to expose
+      target: 8080
+      published: 8080 # this is useful for running locally
+
+```
 
-One thing to keep in mind is that, at the time of this writing, Defang identifies services by the [user/account name](./accounts.md) and the service name (as defined in the `compose.yaml` file). This means that if you have multiple Defang projects with the same service name, they will conflict with each other. We plan to provide a more robust system for managing service names and protecting against conflicts in the future.
+## Compose Top-level Properties
+Here are a list of top-level properties of the [Compose specification](https://docs.docker.com/compose/compose-file/) that Defang supports when writing a `compose.yaml` file.
 
-## Configuration
+### `services`
+(Required)
 
-If you have a service that depends on a [config value](./configuration.md) (such as an API key), you can set it using the CLI:
+The services defined in your application. 
 
+```yaml
+services:
+  service:
+    # add service-level properties here
 ```
-defang config set MY_API_KEY
+
+:::info 
+Defang identifies a service based on your username, project name, and the service name you've defined under the `services` property. See our [Services](/docs/concepts/services) page for more about how Defang resolves service names.
+:::
+
+### `networks`
+(Optional)
+
+The networks defined in your application. This is commonly added together with a [service-level `networks`](#networks-1) property. 
+
+```yaml
+networks:
+  public: 
 ```
 
-and then connect it to the service by specifying it in the `compose.yaml`:
+See our [Networking](/docs/concepts/networking) page for more.
+
+### `volumes`
+(Not yet supported)
+
+The volume mounts for a container, reusable across services. This feature is not currently supported by Defang.
+
+```yaml
+# volumes:
+#   db-data:
+```
+
+:::warning
+Defang does not support the `secrets` top-level property. Please read our [Configuration](/docs/concepts/configuration) page for more. 
+:::
+
+## Compose Service-level Properties
+Here are a list of service-level properties of the [Compose specification](https://docs.docker.com/compose/compose-file/) that Defang supports when writing a `compose.yaml` file.
+
+:::tip
+Service-level means inside your `service`. A service-level property called `build` would look like:
+```yaml
+service:
+    build: ...
+```
 
+Note that in your Compose file, you will need a top-level property called `services` to contain all of your services. For example:
 ```yaml
 services:
-  my-service:
-    environment:
-      - MY_API_KEY
+    service:
+        build: ...
+```
+:::
+
+### `build`
+(Required, unless `image` is defined)
+
+The [build configuration](https://github.com/compose-spec/compose-spec/blob/main/build.md). This property describes how to create an OCI container for this service.
+
+```yaml
+build:
+  context: .
+  dockerfile: ./Dockerfile
+```
+
+### `image`
+(Required, unless `build` is defined)
+
+[This property](https://github.com/compose-spec/compose-spec/blob/main/05-services.md#image) describes the image from which your container should start.
+
+```yaml
+image: nginx:latest
+```
+
+### `ports`
+(Optional, but required if you want to access the service from outside the container)
+
+The ports to expose. The default port mode is `ingress`.
+
+```yaml
+ports:
+  - mode: ingress
+    target: 80
+    published: 80
+```
+
+:::info
+Defang ignores `published` ports in production. As such, it is common to make `target` and `published` ports the same when using Defang. However, it can be useful to include a `published` port for local development, such as Docker.  
+:::
+
+### `command`
+(Optional)
+
+The command which will be run to start your service. If left out, the command from the Docker image will be used.  
+
+```yaml
+command: nginx -g 'daemon off;'
+```
+
+### `deploy`
+(Optional)
+
+The [Deploy Specification](https://github.com/compose-spec/compose-spec/blob/main/deploy.md) describes the runtime constraints and requirements for how your services will be deployed and managed across different environments (e.g. memory reservations, replicas, number of CPUs, etc.).
+
+```yaml
+deploy:
+  replicas: 1
+  reservations:
+    cpus: '0.5'
+    memory: 256M
+```
+
+### `depends_on`
+(Not yet supported)
+
+This property describes startup dependencies between services. This feature is currently unsupported by Defang, but can be useful in local developments such as Docker. 
+
+```yaml
+# depends_on: 
+#   - db
 ```
 
+### `environment`
+(Optional)
+
+The environment variables to set.
+```yaml
+environment:
+  DATABASE_USER: someuser
+```
 :::info
-Read more about configuration in the [Configuration page](./configuration.md).
+For sensitive environment variables (or secret values), you should list the variable's name with a blank or `null` value, and then securely set their actual value with `defang config` in the CLI. See our [Configuration page](/docs/concepts/configuration) for more.
+
+ For example:
+```yaml
+  - DATABASE_USER=someuser # env var loaded with this literal value
+  - DATABASE_PASSWORD # env var loaded using defang config
+```
 :::
+
+### `healthcheck`
+(Optional, but required for healthchecks on services with a published port)
+
+[This property](https://github.com/compose-spec/compose-spec/blob/main/05-services.md#healthcheck) describes a check that will be run to determine whether or not a service's containers are "healthy". It works in the same way, and has the same default values, as the [HEALTHCHECK Dockerfile instruction](https://docs.docker.com/engine/reference/builder/#healthcheck) set by the service's Docker image. Your Compose file can override the values set in the Dockerfile.
+
+When using Defang, your Compose file must have a healthcheck if you want to expose an `ingress` port—even if your Dockerfile already contains one.
+
+:::note
+`curl` is commonly used for containers with an Ubuntu-based image, and `wget` is used for containers with an `alpine`-based image. 
+:::
+
+```yaml
+healthcheck:
+  test: ["CMD", "curl", "-f", "http://localhost:8080/"]
+  interval: 30s
+  timeout: 90s
+  retries: 3
+```
+
+or
+
+```yaml
+healthcheck:
+  test: ["CMD", "wget", "--spider", "http://localhost:8080/"]
+  interval: 30s
+  timeout: 90s
+  retries: 3
+```
+
+### `networks`
+(Optional)
+
+The network configuration. Can be `public`, where Defang will assign a public IP address, or `private`, in which Defang will not. To avoid warnings, add this to the [top-level `networks`](#networks) property as well. 
+
+```yaml
+networks:
+  public: 
+```
+
+You can also assign an alias for a network by using `aliases`, as seen below:
+```yaml
+networks:
+  public: 
+    aliases:
+      - app
+```
+
+See our [Networking](/docs/concepts/networking) page for more.
+
+### `restart`
+(Optional, but highly recommended)
+
+The restart mode for a container. Defaults to `unless-stopped` unless otherwise specified. 
+
+```yaml
+restart: unless-stopped
+```
+
+### `volumes`
+(Not yet supported)
+
+The volume mounts for a container, specific to a service. This feature is not currently supported by Defang.
+
+```yaml
+# volumes:
+#  - "./backend:/app"
+```

docs/concepts/configuration.md

@@ -19,6 +19,9 @@ defang config set API_KEY
 
 You can use sensitive config by specifying them in the `environment` section of a service in a `compose.yaml` file without any value, or by specifying an environment key with a `null` value in your Pulumi code.
 
+Either one of list notation or map notation is acceptable for defining your environment variable(s). See below for an example of each.
+
+#### With List Notation
 ```yaml
 services:
   service1:
@@ -27,9 +30,7 @@ services:
       - API_KEY
 ```
 
-You can also use this syntax:
-
-
+#### With Map Notation
 ```yaml
 services:
   service1:

docs/concepts/domains.mdx

@@ -30,7 +30,7 @@ https://<username>-<service-name>--<port>.defang.dev
 If you're using [Defang BYOC](./defang-byoc.md), your domain will be:
 
 ```
-https://<service-name>--<port>.<username>.defang.app
+https://<service-name>--<port>.<project-name>.<username>.defang.app
 ```
   </TabItem>
 </Tabs>

docs/concepts/services.md

@@ -4,18 +4,39 @@ description: Defang allows you deploy services, defined as containers, to the cl
 sidebar_position: 200
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 # Services
 
-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:
+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.
+
+### Service Name Resolution
 
-`<username>-<service-name>`
+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.
 
-You can learn more about accounts and usernames in the [Accounts page](./accounts.md).
 
 :::tip
-Service names are defined in your Compose file or your Pulumi program.
+Service names are defined in your Compose file or in your Pulumi program.
 :::
 
+<Tabs>
+  <TabItem value="playground" label="Playground" default>
+    Domains for services in Playground follow the following pattern:
+    ```
+    <username>-<service-name>--<port>.prod1a.defang.dev
+    ```
+  </TabItem>
+  <TabItem value="byoc" label="BYOC">
+    Domains for services in Defang BYOC follow the following pattern:
+    ```
+    <service-name>--<port>.<project-name>.<username>.defang.app
+    ```
+  </TabItem>
+</Tabs>
+
+
+### Service Deployment
 Defang manages the deployment process for services. You can learn more about how services are deployed in the [Deployment page](./deployments.md).
 
 :::info