This chapter describes the build steps for Makers deployment and how it works.
When a project is created with a preset template, Makers uses the template's default configuration for building. For an imported GitHub repository, Makers automatically identifies the framework used and applies the most common build configuration.
If you need specific settings, you can customize parameters such as root directory, build command, and output directory when creating a new project or in project settings.
You can start Makers deployment in two ways:
Push code changes to GitHub.
Start up redeployment on the console.
Build Settings
You can specify how Makers builds your project in Project Settings - Build and Deployment Configuration.
Framework Preset
Select a preset framework from the pull-down menu to quickly fill each configuration item. After selecting the framework, you can still adjust other configuration.
Root Directory
The root directory is the path to execute the build command. If not set, it defaults to the repository's root directory ./.
Output Directory
The output directory is the path for storing build artifacts (such as HTML files and static resources). This directory is relative to the root directory and defaults to root ( / ). You can query the output directory for different frameworks through the Construction Guide.
Build Command
Makers automatically sets the build command based on the selected framework, for example npm run build. The build command runs in the Bash shell, and you can also add syntax compatible with Bash.
During build, Makers automatically detects the installation command and installs dependencies from package.json. The default is npm install.
Currently supports the following package managers:
Package Manager
Lock File
Installation Command
Supported Versions
Yarn
yarn.lock
yarn install
1
npm
package-lock.json
npm install
8, 9, 10
pnpm
pnpm-lock.yaml
pnpm install
6, 7, 8, 9
Node Version
Makers pre-installs several Node versions: 14.21.3, 16.20.2, 18.20.4, 20.18.0, 22.11.0, 22.17.1, 22.21.1, 24.5.0, and 24.11.0. You can select one in Project Settings - Node.js Version.
Note:
The pre-installed Node Version includes package managers such as pnpm, yarn, and bun. If there is a .nvmrc file in the project root directory, it will automatically download and switch to the specified version, excluding the appropriate package manager.
Environment Management
Makers provides each project with two deployment environments by default: Production and Preview. Neither can be deleted, and each has its own associated branch, domain, and environment variables. You can view and manage these two environments in Project Settings - Environment Management.
Production: Associates with the production branch (for example, main). Deployments triggered from this branch serve as the production environment and update the live website that users access.
Preview: Associates with all Git branches not assigned to other environments. Deployments triggered from these branches serve as the preview environment, facilitating the preview of new features, bug fixes, or other tests.
Click Edit in the environment operations column to configure the following:
Environment Name and Associated Branch: Production and Preview are system environments. Their names and associated branches are fixed and cannot be modified.
Domain: The access domain bound to this environment.
Auto Deploy: When it is enabled, a new deployment is created for each eligible code commit and merge.
Environment Variables: View and edit the environment variables that take effect for this environment. If a variable also applies to other environments, modifying or deleting it will affect those environments. For more details on environment variables, see the "Environment Variables" section below.
Environment Variable
Makers supports using environment variables to build your project. For each environment variable, you can set the variable name, variable value, remarks, and scope of effect.
To batch import environment variables, paste all environment variables from the .env file into the variable name input box. Makers automatically recognizes them.
Note:
Any changes you make to environment variables will not affect earlier deployments. These changes are applicable only to new deployments.
The variable name has a length limit of 255 bytes, and the variable value has a length limit of 500 bytes.
