Product Introduction
Quick Start
- Importing a Git Repository
- Starting From a Template
- Direct Upload
- Start with AI
Framework Guide
- Frontends
  - Vite
  - React
  - Vue
  - Hugo
  - Other Frameworks
- Backends
- Full-stack
  - Next.js
  - Nuxt
  - Astro
  - React Router
  - SvelteKit
  - TanStack Start
  - Vike
- Custom 404 Page
Project Guide
- Project Management
- edgeone.json
- Configuring Cache
- Building Output Configuration
- Error Codes
Build Guide
Deployment Guide
- Overview
- Create Deploys
- Manage Deploys
- Deploy Button
- Using Github Actions
- Using Gitlab CI/CD
- Using CNB Plugin
- Using IDE PlugIn
- Using CodeBuddy IDE
Domain Management
- Overview
- Custom Domain
- HTTPS Configuration
  - Overview
  - Apply for Free Certificate
  - Using Managed SSL Certificate
- Configure DNS CNAME Record
Observability
- Overview
- Metric Analysis
- Log Analysis
Pages Functions
- Overview
- Edge Functions
- Cloud Functions
  - Overview
  - Node.js
  - Python
  - Go
Middleware
KV Storage
Edge AI
API Token
EdgeOne CLI
Copilot
- Overview
- Quick Start
Pages MCP
Pages Skills
Message Notification
Integration Guide
- AI
  - Dialogue Large Models Integration
  - Large Models for Images Integration
- Database
  - Supabase Integration
  - Pages KV Integration
- Ecommerce
  - Shopify Integration
  - WooCommerce Integration
- Payment
  - Stripe Integration
  - Integrating Paddle
- CMS
  - WordPress Integration
  - Contentful Integration
  - Sanity Integration
  - Payload Integration
- Authentication
  - Supabase Integration
  - Clerk Integration
Best Practices
- AI Dialogue Deployment: Deploy Project with One Sentence Using Skill
- Using General Large Model to Quickly Build AI Application
- Use the DeepSeek model to quickly build a conversational AI site
- Building an Ecommerce Platform with Shopify
- Building a SaaS Site Using Supabase and Stripe
- Building a Company Brand Site Quickly
- How to Quickly Build a Blog Site
Migration Guides
- Migrating from Vercel to EdgeOne Pages
- Migrating from Cloudflare Pages to EdgeOne Pages
- Migrating from Netlify to EdgeOne Pages
Troubleshooting
FAQs
Contact Us
Release Notes

Using CNB Plugin

With this section's guide, you can quickly integrate Cloud Native Build (CNB) into the process for automated build and deploy to EdgeOne Pages.
Configuring a Private Key
Get EDGEONE_API_TOKEN from Pages. For the method for obtaining, see API Token.
Use the CNB key repository for storage, then refer to it in the pipeline. The envs.yml content is as follows:
EDGEONE_API_TOKEN: oJTlMUq9**********NYzKFIw=
The complete .cnb.yml is configured as follows:
# trigger: push to master branch
main:
  push:
    # Import environment variables from private repository:
    # See: https://docs.cnb.cool/en/build/env.html#importing-environment-variables
    - imports: https://cnb.cool/***/-/blob/main/envs.yml
      stages:
        # Build Current Project
        - name: Build Current Project
          image: node:20
          script: node -v && npm install && npm run build
        # Deploy build output to EdgeOne Pages
        # The ./dist directory is generated in the previous build step
        # See: https://www.npmjs.com/package/edgeone
        - name: Deploy to EdgeOne Pages
          image: node:20
          script: npx edgeone pages deploy <outputDirectory> -n <projectName> -t $EDGEONE_API_TOKEN
Note:
npx edgeone pages deploy parameter description:
<outputDirectory>: The folder where the project build product resides (required).
-n, --name: Project name that needs to be deployed. A new project will be created automatically if the project does not exist (required).
-e, --env: Target environment for deployment, available values: production or preview (default production).
Example: npx edgeone pages deploy ./dist -n project-name -t $EDGEONE_API_TOKEN.
Cloud Native Build (CNB)
When code is pushed to the main branch, it triggers the following build process:
1. Import required environment variables.
2. Build project using Node.js 20 environment.
3. Deploy the build output to Pages.
Deploying EdgeOne Pages
The project will be automatically deployed to Pages through the following process after build complete.
1. Build stage generates ./dist directory.
2. Use EdgeOne command line tool edgeone pages deploy to deploy.
More examples
Reference Documentation

Configuring a Private Key
Cloud Native Build (CNB)
Deploying EdgeOne Pages