I'm sorry but I honestly can't think of a single real-life use case.
I do NOT want to instantly deploy to preview on a file save, and certainly not to production. And let's not even talk about working as a team.
The only situation where I can think this is useful is if you write code locally but run your "local" version on a cloud machine. But in that case it's already covered by rsync.
What am I missing?
> Previews in Reflame are accessible at the exact same URL customers will use to access the production deployment, instead of at a different subdomain for each preview (i.e. every preview is accessed through https://reflame.app instead of at https://some-branch-of-reflamedotapp.reflame-previews.dev). Behind the scenes, this is implemented using session cookies that our CDN will check to determine which version of the app to serve.
Also this sounds like the worst idea of the century for many reasons, including security, convenience, reliability, and much more.
I do NOT want to instantly deploy to preview on a file save, and certainly not to production. And let's not even talk about working as a team.
The only situation where I can think this is useful is if you write code locally but run your "local" version on a cloud machine. But in that case it's already covered by rsync.
What am I missing?
> Previews in Reflame are accessible at the exact same URL customers will use to access the production deployment, instead of at a different subdomain for each preview (i.e. every preview is accessed through https://reflame.app instead of at https://some-branch-of-reflamedotapp.reflame-previews.dev). Behind the scenes, this is implemented using session cookies that our CDN will check to determine which version of the app to serve.
Also this sounds like the worst idea of the century for many reasons, including security, convenience, reliability, and much more.