Issue #4 - [BUG] Service discovery fails when Compose Path includes CLI flags

[zenocross]

Description

When a Docker Compose configuration's "Compose Path" includes CLI flags (like -f docker-compose.yml), the service discovery system cannot automatically detect service names, requiring manual input as a workaround.

Current Behavior

• User sets Compose Path with flags: -f docker-compose.yml
• Service discovery attempts to parse path
• Discovery fails due to CLI flag parsing
• Services not automatically detected for domain configuration

Expected Behavior

• System handles Compose Paths with or without CLI flags
• Service names automatically detected regardless of path format
• Fallback to manual input when auto-detection fails
• Clear UI for manual service name entry

Steps to Reproduce

1. Create a Docker Compose application
2. Set Compose Path with CLI flags: -f custom-compose.yml
3. Navigate to domain configuration
4. Attempt to select service for domain routing
5. Service discovery returns no results
6. Manual input required

Root Cause

The service discovery logic assumes a simple file path and doesn't parse CLI flags correctly. When flags are present, the path extraction fails.

Proposed Solution

Add manual input field for service name in domain configuration for Docker Compose applications. This provides:

• Fallback when automatic discovery fails
• Support for complex compose configurations
• User control over service selection

Technical Context

• Component: Domain configuration for Docker Compose
• Type: Feature enhancement with bug fix
• Involves: Service discovery logic, domain form UI
• Requires understanding of Docker Compose CLI flag parsing

---

Download https://cap.so/ to record your screen (use Studio mode). Export as an mp4, and drag and drop into an issue comment below.