Exclude one page from deployment

Hello fellow bubblers,

Has anyone figured out yet how to exclude a page from deployment or deploy only a single page?

I have one page that I can’t update due to examination, but I don’t want that users on that site see the refresh bar when I make changes in my main app.

Would be great if this feature can somehow be created by a workaround!

Unfortunately, there is no way to “exclude” a page from the deployment.

What you could do is put a redirect on this page until it is ready.

The page loads, and then you redirect it to another page.

Would that work for you?

The problem is, the page is already finished. But when I update the main app, I don’t want users on this page to be bothered by updates.

Hence it’s need to be fully isolated from any future updates. The rest of my app takes place on different pages

Huhh

Do you want to be able to update this page without the new deployment warning appearing on the others? Unfortunately, there’s no way to do that.

The best strategy for this is to deploy to the live version at times when there aren’t so many active users.

No, I don’t want to update the page at all :slight_smile: This version that is live needs to stay untouched. But I’m afraid this is not possible

Unfortunately it isn’t possible, only the whole app at a time!

Maybe you can: Create a savepoint, delete the page, push live, revert to the savepoint?

Which plan are you on? Because you could have create custom branches and keep the page there, as you push new updates you would pull/merge so it stays updated.

1 Like

Thanks, that could indeed be a smart solution, only problem is that it will be in dev for ever. I was researching subapps, that might be the best fit. Any experience with that? Im currently on a growth plan

I’m confused.

What’s the issue here? Why can’t you just deploy at a time that won’t disrupt users so much? Or adjust your UX so that state persists on refresh using URL parameters?

Subapps won’t solve your problem, as they still refresh.

1 Like