EdgeOne CLI

Overview

EdgeOne Pages is a front-end development and deployment platform built on Tencent EdgeOne infrastructure, designed for modern web development. It enables developers to quickly build and deploy static sites and serverless applications. By integrating edge function capabilities, it ensures efficient content delivery and dynamic functionality expansion, supporting fast access for users worldwide.

EdgeOne CLI can help you manage and debug Pages Functions in the project more efficiently.

1. Preparations

- Quickly register and log in to the Tencent Cloud Console using a Gmail account.

- Create a Pages project in the Console, and clone the repository to Local.

_If you are a China site user, please go to the corresponding Pages console._

2. Quick Start

$3

In the cloned project during the preparation stage, you can use npm to install the CLI:

``plaintext
npm install -g edgeone
`

Use the edgeone -v command to check if the installation is successful. Use the edgeone -h command to view all relevant commands.

###

$3

Execute the login command, follow the prompts to select Global (International) or China, then complete the login in the pop-up browser window.

`plaintext
edgeone login
`

After completing the login, you can use the edgeone whoami command to view the current login account information.

$3

After successful login, execute the initialization command to initialize the basic environment required by Edgeone Pages in the project:

`plaintext
edgeone pages init
`

After initialization, an edge-functions or node-functions folder and sample functions will be generated in the root directory of the project. You can continue to add and develop functions in this folder.

$3

After completing initialization, enter the local development stage:

`plaintext
edgeone pages dev
`

The run command by default creates a service locally on port 8088. Both the Pages Function service and the Pages project service run on the same port, with no need for additional proxying.

You can access the front-end page via http://localhost:8088/. In the front-end project, use the Fetch API directly, where the access path is the path of function files in folder edge-functions or node-functions.

`javascript
// ./node-functions/api/my-functions.js
fetch('/api/my-functions', {
method: 'POST',
body: JSON.stringify({ data: 'example' }),
});
`

Note:
- The dev service will read devCommand from edgeone.json to start your dev server. If absent, it will read the dev script from your project's package.json.
- Edge Functions debug service has a limit on the number of times it can start up, so try to avoid frequently logging out and starting the dev service (hot updates within the dev service will not increase the startup count).

$3

If you need to use the Key-Value Storage capability or synchronize the environment variables set in the console to local debugging, you can execute the Associated Project commands, enter the project name as required. The project name here is the one created in the Preparation Work of the Pages project.

`plaintext
edgeone pages link
`
If you need to link a project that does not exist, you can also create a new project directly under the CLI guide.

$3

Build locally and deploy to EdgeOne Pages. If you need to link an existing project, it must be of the direct upload type.

`plaintext
edgeone pages deploy [] [-n ] [-e ]
`

#### Parameters

- : Path of folder or ZIP package to deploy
- -n, --name: Project name for deployment (creates new or updates existing project)
- -e, --env: Environment to deploy to, choices: 'production' or 'preview' (default: 'production')

Note:
- When you execute the deploy command, the CLI will automatically build and deploy your project.
- If you build manually, you need to place the Pages Functions related folders and package.json into the output directory (such as dist), and then run edgeone pages deploy ./dist.

#### Usage Examples

`plaintext


Deploy build folder to production

`plaintext
edgeone switch
`

3. CI/CD Integration

This section provides guidance on integrating EdgeOne CLI into your CI/CD pipelines for automated deployments.

$3

For CI/CD pipelines, you can use the same deploy command with an API Token for authentication:

`plaintext
edgeone pages deploy [] -n -t [-e ]
`

#### Parameters

- : Path of folder or ZIP package to deploy
- -n, --name: Project name for deployment (creates new or updates existing project) (required)
- -e, --env: Environment to deploy to, choices: 'production' or 'preview' (default: 'production')
- -t, --token: API Token for CI/CD pipelines (required for automated deployments)

Note:
- By default, when executing deploy, the CLI automatically builds and packages frontend code, node-functions, and edge-functions into the .edgeone folder and deploy to Pages.
- If you choose to build the project manually, you need to manually copy the Pages Functions related folder and package.json to dist (suppose the output directory is dist), then rerun edgeone pages deploy ./dist.

#### CI/CD Pipeline Examples

`plaintext


Basic CI deployment to production with API token

``

References

Pages Introduction ｜ Pages Functions

_To access the China site documentation, please click here._

Contact

If you need technical support, please contact us.