Skip to content

Commit b7f4730

Browse files
committed
refactor(destinations): update management section and add deletion prerequisites
1 parent 047ef9a commit b7f4730

File tree

3 files changed

+23
-5
lines changed

3 files changed

+23
-5
lines changed

docs/knowledge-base/destinations/manage.md

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ Navigate to **Destinations** to see all your destinations across all servers.
1414
Navigate to **Servers****[Server Name]****Destinations** to view destinations specific to that server.
1515
<ZoomableImage src="/docs/images/destinations/destinations-server-overview.webp" />
1616

17-
## Editing Destination Settings
17+
## Editing & Deleting Destinations
1818

19-
Click on a destination to access its management page where you can either edit or [delete](./delete.md) it.
19+
Click on a destination to access its management page where you can either edit or delete it.
2020

2121
<ZoomableImage src="/docs/images/destinations/destinations-settings.webp" />
2222

@@ -26,22 +26,40 @@ Click on a destination to access its management page where you can either edit o
2626
- **Server IP**: View the server IP address where the destination is hosted (read-only)
2727
- **Docker Network**: View the Docker network name (read-only)
2828

29+
### Before You Delete
30+
31+
#### Check for Active Resources
32+
33+
Coolify won't allow you to delete a destination that has active resources. Therefore, before deleting a destination, ensure it's not being used:
34+
35+
1. **Applications**: No applications deployed to this destination
36+
2. **Databases**: No databases running in this destination
37+
3. **Services**: No services configured for this destination
38+
39+
#### Resource Dependencies
40+
41+
Verify that no other resources depend on this destination, to avoid issues after deletion:
42+
43+
- **Environment Variables**: Check for hardcoded references
44+
- **Network Dependencies**: Ensure no cross-destination communication
45+
- **Proxies & Load Balancers**: Update load balancer and proxy configuration
46+
2947
## Assign Resources to a Destination
3048

3149
When you have more then one destination on a server, you will get prompted to select a destination when creating a new resource.
3250

3351
<ZoomableImage src="/docs/images/destinations/destinations-selection.webp" />
3452

35-
If your resource is already created, you can make a **Copy** of it to another destination:
53+
If your resource is already created, you can make a **Clone** of it to another destination:
3654

37-
<ZoomableImage src="/docs/images/destinations/destinations-copy.webp" />
55+
<ZoomableImage src="/docs/images/destinations/destinations-clone.webp" />
3856

3957
1. Navigate to the resource's management page over the **Projects** tab.
4058
2. Go to **Resource Operations**
4159
3. Select the destination
4260

4361
::: warning
44-
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.
62+
Cloning 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.
4563
:::
4664

4765
### Service Stacks
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)