Issue #254 opened: application update: support custom_network_aliases (app-to-app DNS)

Problem

Coolify only gives database containers a uuid DNS hostname (their container name IS the uuid). Application containers get <uuid>-<deploy-suffix> names that change every deploy — so there is no stable DNS name for app-to-app traffic on a shared network, and the MCP offers no way to create one.

Hit this wiring edator-cloud → edator-asr (Whisper sidecar) on the coolify network:

• ASR_URL=http://<app-uuid>:9000 → cURL error 6: Could not resolve host (uuid aliases are a DB-only convenience)
• --network-alias in custom_docker_run_options → silently ignored by Coolify
• application update with custom_network_aliases → rejected (Invalid request) — the field isn't in the MCP's schema or types (checked src/types/coolify.ts @ 2.13.0)

Coolify supports it — verified

The Coolify API (4.1.2) accepts the field directly:

curl -X PATCH $COOLIFY_BASE_URL/api/v1/applications/{uuid} \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \
  -d '{"custom_network_aliases": "edator-asr"}'
# → {"uuid":"..."} — persists, and after a redeploy the alias resolves on the destination network

That's how edator-asr is wired today (worked around the MCP with a direct PATCH).

Ask

Add custom_network_aliases?: string to the application update tool schema + src/types/coolify.ts so inter-app DNS is configurable through the MCP. Bonus: mention in the tool description that app containers do NOT get uuid hostnames (databases do) — that asymmetry cost two failed E2E runs to discover.

🤖 Generated with Claude Code