Migrate customizations

When a new version of GBC is released, you must take these steps to move your existing customization projects.

Before you begin

You must have downloaded and set up the project directory for the latest version; see Set up your GBC build environment.


To avoid overwriting your existing GBC project, unzip the project package in a new directory.

  1. Set up your new customization project directory.

    This involves installing the dependencies for Node.jsĀ® within your project directory using npm install and gbc commands.

    $ cd gbc-project-dir
    $ npm install
    $ gbc build
  2. Copy the customization directories from the previous GBC project and add them to gbc-project-dir/customization.
  3. If you added global theme parts in the previous GBC project, move those global theme parts into your new project. To keep them global, copy those theme part directories and add them to gbc-project-dir/theme. Alternatively, you can use this opportunity to move them into a local theme parts directory.

    Prior to 1.00.52, all theme parts were stored in the global directory gbc-project-dir/theme. As part of the migration, it is recommended that you move those theme parts into the local theme parts folder for the customization, gbc-project-dir/customization/customization-project-dir/theme.

  4. If you modified any of the default global theme part directories, examine any changes to the most recent default theme parts, and merge your changes accordingly.
  5. Build the customizations.

    Using the gbc command, recreate the distributable clients for each of your customizations in the gbc-new-project-dir/customization path.

  6. Deploy your customization to the Genero Application Server. See Build and deploy a GBC runtime package.

    For a production environment, you must deploy the customization to the GAS.


    To ensure a smooth migration, clear your cache after upgrading. You may also need to clear the local storage.