feat(destinations): add resource assignment section

Author: Cinzya

docs/knowledge-base/destinations/manage.md

@@ -1,6 +1,6 @@
 # Managing Destinations
 
-Learn how to manage your existing destinations in Coolify, including editing, monitoring, and deleting them.
+Learn how to manage your existing destinations in Coolify, and how to assign resources to them.
 
 ## Viewing Destinations
 
@@ -26,6 +26,34 @@ Click on a destination to access its management page where you can either edit o
 - **Server IP**: View the server IP address where the destination is hosted (read-only)
 - **Docker Network**: View the Docker network name (read-only)
 
+## Assign Resources to a Destination
+
+When you have more then one destination on a server, you will get prompted to select a destination when creating a new resource.
+
+<ZoomableImage src="/docs/images/destinations/destinations-selection.webp" />
+
+If your resource is already created, you can make a **Copy** of it to another destination:
+
+<ZoomableImage src="/docs/images/destinations/destinations-copy.webp" />
+
+1. Navigate to the resource's management page over the **Projects** tab.
+2. Go to **Resource Operations**
+3. Select the destination
+
+::: warning
+Copying a resource to another destination will create a new instance of that resource. This will not move the resource or it's data but create a duplicate.
+:::
+
+### Service Stacks
+
+Unlike applications or databases, service stacks are not by default connected to the assigned destination. This also includes applications using the [Docker Compose Build Pack](/builds/packs/docker-compose). Coolify creates an isolated network for each service stack, allowing you to run multiple instances of the same service on the same server without conflicts.
+
+If you want to connect a service stack to a destination, enable [Connect to Predefined Networks](/knowledge-base/docker/compose#connect-to-predefined-networks) in it's settings. This allows the service stack to communicate with other resources on the same destination.
+
+::: danger WARNING
+Avoid defining network configurations directly in your service stack's `docker-compose.y[a]ml` and instead use Coolify's Destination settings to manage network connections. This could otherwise lead to undesired behavior, such as **Gateway Timeout** errors.
+:::
+
 ## Best Practices
 
 1. **Naming Convention**: Use descriptive names for destinations