Fix swagger host for configured api server address and port

[icyleaf]

Bug Fix: Swagger Host Not Updated with Dynamic Address and Port

When the server starts with a custom port (via CLI flag -p or PC_PORT_NUM environment variable), the Swagger documentation should reflect the actual server address and port instead of showing the hardcoded default localhost:8080.

Problem

Currently, the interactive Swagger UI at /swagger/index.html always shows localhost:8080 as the host, even when the server is running on a different port or address configured through:

• CLI flag: process-compose -p 9090
• Environment variable: PC_PORT_NUM=9090 process-compose

This causes the Swagger UI to fail to communicate with the API when using non-standard ports.

Solution

Update the SwaggerInfo.Host dynamically in the StartHttpServerWithTCP() function before the router is created. The SwaggerInfo variable is already exported and designed to be modified at runtime (as indicated by its comment: "holds exported Swagger Info so clients can modify it").

Changes Required

Modify src/api/server.go:

1. Import the docs package
2. Add code to update docs.SwaggerInfo.Host with the actual address and port in StartHttpServerWithTCP() function

Implementation Details

• Add import: "github.com/f1bonacc1/process-compose/src/docs"
• In StartHttpServerWithTCP(), add at the beginning (before router := getRouter(...)):

docs.SwaggerInfo.Host = fmt.Sprintf("%s:%d", address, port)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud