Pick a frontend repository from Github
• The repositories in your Github account you are connected to are listed. If you have given permission for a single repository on GitHub, one repository will be listed, if you have allowed all repositories, all repositories will be listed.
• The existing repository as Public or Private is displayed on the repository list.
• You can search by repository name from the Search field.
• After selecting the repository, the Next button displays active.
• Click the Next button to proceed to the next step.
• If a previously used repository is selected again in the application, the system will display a warning message. You need to select a new repository.
Front-end Basic Build Settings
• Base directory: Specifies the directory that our buildbot changes to before starting a build. It’s where our build system checks for dependency management files such as package.json or .nvmrc. If not set, the base directory defaults to the root of the repository.
• Build command: where you should specify the command to run to build your site if you are using a static site generator or other build tool. For example, npm run build. The build command runs in the Bash shell, allowing you to add Bash-compatible syntax to the command.
• Publish directory: directory (relative to the root of your repo) that contains the deploy-ready HTML files and assets generated by the build. If a base directory has been specified, it should be included in the publish directory path. For example, if your base directory is set to site, the publish directory should include the site/ prefix like so: site/public.
• Default branch: Set the branch that will be deployed on changes and manually.
Front-end Environment Variables
Environment variables allow you to configure your site’s build and functionality based on different parameters and deploy contexts. Environment variables are accessible during your build. This allows you to change behaviors based on deploy parameters or to include information you don’t want to save in your repository, such as API keys.
To use these environment variables, you need to ensure they’re set in the environment where the build will run - on NuCAL application through continuous deployment or in your local development environment.
Things to Pay Attention
• Maximum 10 environment variables can added.