-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Fix env variables in convex.yaml
#7208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
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 `SERVICE_URL_SITE_3211` for site url support. Without this, http actions will have to go to `${SERVICE_URL_BACKEND}/http`
|
Hi @hahagu! 👋 It appears to us that you are either adding a new service or making changes to an existing one. Coolify Docs Repository: https://github.com/coollabsio/coolify-docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commented out SERVICE_URL_SITE_3211 and updated CONVEX_SITE_ORIGIN note.
|
There's currently no way to have a single service with two ports have urls generated for on coolify. |
There's currently no way to have a single service with two ports have urls generated for on coolify. So, we make use of an nginx proxy for the site.
Fix accidentally edited variables in convex.yaml
@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. |

Changes
Fix env variables
CONVEX_CLOUD_ORIGINandCONVEX_SITE_ORIGINto be proper values.Otherwise, you will get a 404 error running queries/mutations from actions.
Also added nginx with
SERVICE_URL_SITEfor site url support. Without this, http actions will have to go to${SERVICE_URL_BACKEND}/httpIssues