Once your customization is ready, you need to build the GBC runtime that your BDL development team will be able to deploy on their development or production environments.

The command creates a zip file for the customization using the settings of the compile.mode and compile.customization parameters in gbc-project-dir/custom.json. To produce a runtime package using the settings of the custom.json file, execute:

$ gbc build --create-zip

You may wish to switch modes (cdev, dev, prod). To accomplish this, either change the compile.mode parameter in gbc-project-dir/custom.json or use the --compile-mode option of the gbc build command.

You may wish to switch customizations. To accomplish this, either change the compile.customization parameter in gbc-project-dir/custom.json or use the --customization option of the gbc build command.

This example specifies both the mode and customization:

gbc build --customization customization/myCustomization --compile-mode prod --create-zip

The resulting runtime will be located in gbc-project-dir/archive directory. It will be named fjs-gbc-version.suffix-buildbuild-customization_customName.zip. This is a GBC runtime that you can deploy. You can deploy it in the same manner as you deploy the standard runtime provided by Four Js on our web site download center. See Deploy runtime on GAS.

NOTE: You can rename this file to something shorter and easier to manage.

By default, the customization suffix is "c". To change the suffix used for a customization, see Change the version customization suffix.