X

The Visual Builder Cloud Service Blog

  • August 14, 2019

Importing and Updating Apps Between Visual Builder Instances

Shay Shmeltzer
Director of Product Management - Oracle
This is a syndicated post, view the original post here

Visual Builder has built in lifecycle for applications that supports hosting the development, test, and production instances of an app on a single server. But many companies prefer to separate their dev instances from their production instances - this allows them to separate the users accessing each instance, separate the backends that they are accessing, and guarantee that there is no development load on the production server. If that is the approach taken, you'll need to promote the app from the development VB instance to the production VB instance, and also take care of subsequent changes to the app.

The solution for this need is the use of a shared code repository - which is available for you for free in the Oracle Developer Cloud.

If you haven't yet watched the video that explains how to setup Visual Builder to work with the Git repository in Developer Cloud - you should watch that video first. This is an essential thing to do if multiple developers are working on your project. It is also the thing that will enable you to promote code between environments.

Once your app code is inside the Git repo - you can leverage Visual Builder's "Import from Git" option in any other instance of VB - this will create your initial version of the app on your new instance.

When someone changes the code in the repository (for example by checking in the latest changes from the development instance), you can pick up those changes in your production VB instance by connecting your app back to that git repository (and the specific branch you want to use) and doing a Reset Head operation - this will overwrite your local app definition on the production instance with the latest updates from your dev instance. 

Note that if you already have a published application which is live, you would first need to create a new version of this app, so you could make changes to the code. Then you reset the code from head, and then you re-stage and re-publish the app. Your changes will be reflected in the running app as soon as you do this.

And don't worry - as part of the re-publish step we will ask you what to do with the existing data in your business objects - just choose the option to "Keep existing data in live" and your data will stay as is while the rest of the app gets updated.

Publish app dialog

In the video below you can see the full process:

Note that in the video the process is done manually, if you are adopting DevOps automation approach you should look into the ability to use the build jobs in Developer Cloud to automate the process of staging and publishing apps each time code changes in a specific branch. This blog entry can get you started on your way to DevOps Visual Builder.

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.