-
Notifications
You must be signed in to change notification settings - Fork 67
Workers support to use SSL for SaaS #267
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
Comments
If I understand properly @timhanlon, you want the ability to set multiple custom domain for a project? On Pages, I can do this and the customer only have to set the CNAME on his DNS (expect for APEX). I am happy to better understand what you are building to better serve your purpose! |
Ah, I wasn't aware that external domains on Pages was an option. Couple of things:
|
I'm also having the same issue ATM. Now having to change my entire plan, and have to move with this https://developers.cloudflare.com/workers/frameworks/framework-guides/nuxt/ instead of using NuxtHub for customer facing part. I think it should be the top priority as per the situation of pages vs worker. |
@Ain477 Here's the workaround I'm using at the moment, in case it helps. It's a self-hosted setup and it loses the CI/CD, but I can use all the Nuxt Hub primitives in a Nuxt app on Workers and have a customers.[app].com origin for customers to CNAME to. The only issue I had was working around the difference in how Workers/Pages handles env variables. Using pnpm patch to patch @nuxthub/core:
|
Is your feature request related to a problem? Please describe.
SSL for SaaS is not compatible with Cloudflare Pages, which is a blocker to doing SaaS with custom user domains on Nuxt Hub.
Describe the solution you'd like
The ability to deploy Nuxt Hub apps using module format Workers instead of Pages.
Describe alternatives you've considered
The only workaround I'm aware of is setting up a Worker for the fallback origin which proxies requests to Pages, however I'm getting
D1_TYPE_ERROR
when using D1 in API routes on the proxy. The only workaround I've found there is directly hitting the API routes on the domain which is assigned to Pages, which isn't ideal.The text was updated successfully, but these errors were encountered: