Activity

Bug Description

When creating or updating applications with a custom domain using the fqdn field, the domain setting is silently ignored by the Coolify API.

Root Cause

The Coolify API expects the field to be named domains, not fqdn. The following methods pass fqdn directly in the request body without mapping it:

• createApplicationPublic
• createApplicationPrivateGH
• createApplicationPrivateKey
• updateApplication

Steps to Reproduce

await client.createApplicationPublic({
  project_uuid: 'proj-uuid',
  server_uuid: 'server-uuid',
  git_repository: 'https://github.com/user/repo',
  git_branch: 'main',
  build_pack: 'nixpacks',
  ports_exposes: '3000',
  fqdn: 'https://app.example.com', // ← this is never applied
});

Expected Behavior

The application is created with https://app.example.com as its domain.

Actual Behavior

The domain is not set because the Coolify API receives fqdn instead of domains and ignores it.

Fix

Map fqdn → domains before sending the request to the API. A mapFqdnToDomains helper should be applied in all 4 affected methods to transparently convert the field while preserving backward compatibility for callers.