Fix env variables in convex.yaml

[hahagu]

Changes

• Fix env variables CONVEX_CLOUD_ORIGIN and CONVEX_SITE_ORIGIN to be proper values.
  Otherwise, you will get a 404 error running queries/mutations from actions.

• Also added nginx with SERVICE_URL_SITE for site url support. Without this, http actions will have to go to ${SERVICE_URL_BACKEND}/http

Issues

• fix [Bug]: Incorrect Environment Variables in Convex Deployment Template #5569
• fix [Bug]: Convex PUBLIC_CONVEX_SITE_URL is not exposed correctly #7232

[github-actions]

Hi @hahagu! 👋

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

[orenaksakal]

[hahagu]

There's currently no way to have a single service with two ports have urls generated for on coolify.
Therefore, I have commented out SERVICE_URL_SITE_3211.

[Cinzya]

There's currently no way to have a single service with two ports have urls generated for on coolify.
Therefore, I have commented out SERVICE_URL_SITE_3211.

@hahagu does this mean users need to add those two URLs with their dedicated ports manually? Or did you find a different workaround? Would be good if you could include that information to the Coolify Docs, so people understand better what to do.

[hahagu]

There's currently no way to have a single service with two ports have urls generated for on coolify.
Therefore, I have commented out SERVICE_URL_SITE_3211.

@hahagu does this mean users need to add those two URLs with their dedicated ports manually? Or did you find a different workaround? Would be good if you could include that information to the Coolify Docs, so people understand better what to do.

Implemented a nginx proxy as a workaround.

[hahagu]

@Cinzya Please review, thanks!

[KazBrekker1]

I tried the yml but i faced an issue opening the dashboard, for some reason initially it shows that the backend is not running, and then after the following log errors, it connects successfully.

[peaklabs-dev]

The fact that we cannot generate multiple domains with different ports for one container is most likely a parser bug. I have let Andras know internally and once the bug is fixed the template can be properly updated without an additional proxy.