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.

Creating Projects

Select "direct upload" via the "create project" option on the Makers console homepage.





After filling in the "project name" and "acceleration region", drag and drop the project assets to the designated region.



Click start deployment. After uploading the assets, the project will start creation and go to the deployment details page. After successful deployment, you can view the project through the preview URL.

Create a New Deployment

After creating a project, you can release a new version by clicking "create deployment" on the deployment page.



Drag and drop the new version asset of the project to the specified region. The deployment environment defaults to "production environment" and can be switched to "preview environment".



Note:

Production environment: update to the online website users access, effective immediately.

Preview environment: verify changes in an isolated environment without affecting official data.

Upload Content Requirements

The uploaded content must meet the following requirements; otherwise, the upload may fail or the deployment may become inaccessible after deployment:

Directory structure: It supports uploading a single folder, a single ZIP compressed package, or a single HTML file. It does not support selecting multiple scattered files or multiple folders at once.

Entry file: The root directory of the uploaded content must contain index.html as the website entry point (default document). When uploading a ZIP or folder, ensure index.html is at the outermost level of the compressed package / folder. Avoid an extra directory layer (for example, dist/index.html inside the ZIP instead of index.html under the root directory). Otherwise, accessing the website homepage will return a 404 error.

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

Upload Limit

In direct upload method, the project asset is limited to 20000 files with a single file size of 25MB.

If the limit is exceeded, a red warning will appear in the upload area. You can adjust the project asset and reupload, or use the EdgeOne CLI deploy command to upload. For specific operation method, refer to document.

Note:

Uploading folders with many files may be time-consuming. It is advisable to compress them into a ZIP file to enhance upload speed.

Supported File Types

Direct upload currently enables individually a ZIP compressed package, HTML file, or folder.

Function and Edgeone.Json

Direct upload also supports Makers Functions and the project configuration file edgeone.json. You only need to place the edge-functions and cloud-functions folders, along with edgeone.json, in the root directory.



For more information about functions, see the Functions documentation.

Note:

For direct upload, the edgeone.json file support only redirects, rewrites, headers, and caches field settings. For details, see edgeone.json document.