Development Packages and Deployment

Idea
1

The ability to deploy specific changes is great. However, I often run into issues where I’d like to be “in progress” on multiple different updates and work on them over several days/weeks before deploying. I’m used to working on platforms where you can create development packages and send all the build related to a package up to live whenever you want. It would be great to see something like that on Bubble. Here’s a thought:

  1. When you launch an app you are prompted to choose an existing “package” or create a new one.
  2. When you are working in a package, all changes you make are saved to that package - beyond the current working session, so you can work over months if you want.
  3. When you go to deploy, you have the option of full app deployment or session deployment like today, but you also have the option to deploy a “package” which contains all edits for the related package.

This would make my life easier…especially when working in teams with different responsibilities and with projects that take more than a few minutes/hours to complete. I’ve also run into some issues where Chrome will crash from resource constraints and then my session changes are lost…

3 Likes
2

On that note, would also be awesome if those packages could be sent to other copies of an app - say you have a demo version and a training version and they each have their own database (for demo or training purposes) - you want to be able to push new build out to those without having to rebuild their unique databases.

1 Like
3

I agree that it’d be nice to have more robust version control capabilities and I suspect Bubble will build them at some point.

In the meantime, here’s a workaround that we use which gives us more control over the version of code that’s pushed live, in case this approach is helpful for anyone else.

1 Like