Skip to content
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

[Feature]: Control whether the Pages ability is applied #470

Open
yveeven opened this issue Feb 14, 2025 · 3 comments
Open

[Feature]: Control whether the Pages ability is applied #470

yveeven opened this issue Feb 14, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@yveeven
Copy link

yveeven commented Feb 14, 2025

Is your feature request related to a problem? Please describe.
When users only want to use DB, KV, and other capabilities without exposing their applications to the Internet

Describe the solution you'd like
If there is a switch that can control "whether you need a page or not", and pages are not deployed when closed, I think it may be better, and the deployment speed will be faster.

Describe alternatives you've considered
I may currently choose to set the branch to be empty.

@yveeven yveeven added the enhancement New feature or request label Feb 14, 2025
Copy link
Contributor

atinux commented Feb 14, 2025

I am not sure to fully understand your use case here

@yveeven
Copy link
Author

yveeven commented Feb 15, 2025

I think I can explain in more detail:
I know nuxthub is based on cloudflare, so the relevant capabilities are based on automatically creating an application in cloudflare, which will carry the domain name by default, but in fact I use nuxthub as a supabase alternative, I just need the backend capabilities, I may not need the domain name to open application access, I'm not sure if this requirement is reasonable based on cloudflare, but I think some private use cases or projects are normal, not all require a domain name

@yveeven
Copy link
Author

yveeven commented Feb 15, 2025

I just noticed something about cloudflare access, I think it has solved the problem, I think it can be turned off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants