Direct Upload

You can directly upload the built assets of your project to Makers and deploy them to the EdgeOne global network. If you need to integrate your own build platform or upload from a local computer, you should choose direct upload instead of importing a Git repository.

Note:

Select direct upload and you will be unable to switch to Git integration. You must create a new project with Git integration to use automatic deployment.

1. Creating a Project

1. On the Makers console homepage, click Create Project and select Direct Upload.



2. Enter the "Project Name" and select the "Acceleration Region".

Note:

Project Name: It must be 5-50 characters in length and can only contain lowercase letters, digits, and hyphens. Hyphens cannot be used at the beginning, at the end, or consecutively.



3. Drag the built assets of your project to the designated area. When assets are uploaded directly, no build process is executed on the platform side (meaning commands such as npm install and npm run build are not run). Please upload the pre-built static artifacts, not the unbuilt source code.

Note:

Before uploading, confirm the following requirements:

Upload format: Only a single folder, a single ZIP archive, or a single HTML file can be uploaded. Selecting multiple scattered files or multiple folders at once is not supported.

Entry file: The root directory of the uploaded content must contain index.html as the website entry point. When uploading a ZIP archive or folder, ensure that index.html is at the outermost level of the archive or folder. Avoid placing it within an extra directory layer (for example, having dist/index.html inside the ZIP instead of index.html at the root). Otherwise, accessing the site's homepage will return a 404 error.

File naming: File names must not contain illegal characters \ / : * ? " < > |.

File quantity and size: A project's assets can contain a maximum of 20,000 files, with each individual file not exceeding 25 MB. If these limits are exceeded, a red warning appears in the upload area. You can adjust the project assets and upload again, or use the deploy command in EdgeOne CLI to upload and deploy. For specific instructions, see the EdgeOne CLI documentation.

Upload speed: Uploading a folder containing many files may take a long time. It is recommended to compress it into a ZIP file first and then upload it.



4. Click Start Deployment. After the assets are uploaded, the system creates the project and redirects you to the deployment details page. Once the deployment succeeds, you can view the project via the preview link.

2. Creating a New Deployment

1. After creating a project, go to the Build & Deploy page and click New Deployment to publish a new version.



2. The deployment environment is set to "Production" by default. You can also switch it to "Preview". Drag the assets of the new project version to the designated area.

Production: Updates are applied to the live website that users access and take effect immediately.

Preview: Changes are validated in an isolated environment without affecting production data.



3. Functions and edgeone.json

The direct upload method also supports Makers Functions and the project configuration file edgeone.json. To use this, simply place the edge-functions and cloud-functions folders, along with the edgeone.json file, in the root directory.



For more information about functions, see the Functions documentation.

Note:

For direct upload, the edgeone.json file supports only the redirects, rewrites, and headers field settings. For details, see the edgeone.json documentation.