Can we customize the convex public/deployment url?
If yes, how? Are there any docs/tutorial for this?
10 Replies
Not yet but we're working on it. For your use case, which of these apply:
1. You have a domain like
myapp.com for your website and you want to use api.myapp.com so the network traffic looks more professional
2. You want to make a standalone API and give out a nicer URL to customers - e.g. myapi.com
And how would you want to customize the .convex.cloud URL (which is used by clients, websocket, etc. and has endpoints defined by Convex) vs. the .convex.site URL (which serves your http actions and is fully controlled by you)#1
@ian
For production:
Option #1 would be best - api.domain.com
For .convex.cloud url, it can be cloud.domain.com and for .convex.site url it can be site.domain.com or static.domain.com (It would be best if you recommend the naming conventions for this).
How would this work for development/staging environments?
Will this also introduce latency when making requests?
there will be no additional latency re the routing, DNS requests to the subdomain will go straight to convex servers not proxied through your hosting provider
the plan is that this would be purely for production deployments since these are the ones that are actually serving customer traffic and behind a custom domain. dev/preview deployments will just have the convex backend domain name
Great, when can we expect this functionality?
we're actively working on it right now, along with a lot of other things of course, so expect to have this ready in around a month
Thats amazing, thank you @james
Hey @james - any updates on this?
Still an active project! In the process we’re redesigning our api/traffic layer to support scaling out Convex, as well as custom domains. @gautamg is working on both and we’ll give an update when they start rolling out.
Lovely, thanks mate appreciate the update