feat(service): add EMQX

[MohmmadQunibi]

Changes

Added an emxq service template

Category

• Adding new one click service

Preview

AI Assistance

• AI was used (please describe below)

If AI was used:

• Tools used: Claude code
• How extensively: make sure i missed nothing for the configuration

Testing

I had a coolify instance running and updated the files there to have these changes and then called php artisan generate:services

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.

[github-actions]

Hi @MohmmadQunibi! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

[ShadowArcanist]

Could you please share the steps you followed to test this service on Coolify?

[MohmmadQunibi]

Could you please share the steps you followed to test this service on Coolify?

Done

[ShadowArcanist]

Some ports are not mapped to host which is fine, please mention this on our docs and write a simple guide to map port to host by editing the compose.

• 1883 → MQTT over TCP (standard, unencrypted)
  • This is the main port IoT devices use to publish/subscribe.
• 8883 → MQTT over TLS/SSL (secure MQTT)
  • Same protocol as 1883 but encrypted.
• 8083 → MQTT over WebSocket (WS)
  • Used for browser-based clients or HTTP-friendly MQTT connections.
• 8084 → MQTT over Secure WebSocket (WSS)
  • WebSocket + TLS (secure browser/device communication).

[MohmmadQunibi]

Some ports are not mapped to host which is fine, please mention this on our docs and write a simple guide to map port to host by editing the compose.

• 1883 → MQTT over TCP (standard, unencrypted)

  • This is the main port IoT devices use to publish/subscribe.

• 8883 → MQTT over TLS/SSL (secure MQTT)

  • Same protocol as 1883 but encrypted.

• 8083 → MQTT over WebSocket (WS)

  • Used for browser-based clients or HTTP-friendly MQTT connections.

• 8084 → MQTT over Secure WebSocket (WSS)

  • WebSocket + TLS (secure browser/device communication).

I think mapping them by default is the correct approach since this is a broker those ports will be utilized for sure