-
Notifications
You must be signed in to change notification settings - Fork 789
Description
One reason I prefer deploying to my own Cloudflare account via the GitHub repo instead of using the “Deploy to Cloudflare” button is that, once an app is deployed that way, there’s currently no way to undo or restrict that deployment — other than deploying something else over it.
I’d like to request a “Private Mode” option for deployed versions, similar to how apps themselves can be marked private. When enabled, only the app’s creator should be able to access the deployed instance.
Why this is needed:
The “Deploy to Cloudflare” button is extremely useful for quickly sharing a working version of an app with colleagues or friends, and it’s much faster than deploying via Git or other methods. However, depending on the app’s purpose, not being able to take it down or restrict access can be problematic — especially during early development or testing phases.
Alternatives considered:
- Ask the agent to implement password protection:
Possible, but risky and unnecessarily complex. It also makes it harder to revert to a public state later. - Take down the current deployment:
Would effectively remove all access — including for the app creator — which isn’t ideal either.
Additional context:
After deployment, the user is shown both:
- A link to the deployed version, and
- A “Share Link” to the app page inside the VibeSDK platform.
Below that “Share Link,” there’s a “Make Private” button. However, that button only makes the Share Link private, not the deployed version itself. This can be confusing, since it appears immediately after completing the “Deploy to Cloudflare” process.