Skip to content

docs: add EdgeOne Pages deploy guide - #2372

Open
Ibochkarev wants to merge 3 commits into
nuxt:mainfrom
Ibochkarev:docs/issue-2127-edgeone-pages
Open

docs: add EdgeOne Pages deploy guide#2372
Ibochkarev wants to merge 3 commits into
nuxt:mainfrom
Ibochkarev:docs/issue-2127-edgeone-pages

Conversation

@Ibochkarev

Copy link
Copy Markdown
Contributor

🔗 Linked issue

Fixes #2127

📚 Description

EdgeOne Pages has a Nitro preset (edgeone-pages) but no card on nuxt.com/deploy yet. People looking for Tencent EdgeOne hosting had to dig into Nitro docs alone.

I added an EdgeOne Pages deploy guide covering the console flow with NITRO_PRESET=edgeone-pages, the EdgeOne CLI, and links to the EdgeOne Nuxt guide and Nitro preset docs.

@vercel

vercel Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

@Ibochkarev is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

@Ibochkarev
Ibochkarev marked this pull request as ready for review August 8, 2026 17:33
@Ibochkarev
Ibochkarev requested a review from atinux as a code owner August 8, 2026 17:33
@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@Ibochkarev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dbbbff58-0cda-44d9-aa05-b835871f7c62

📥 Commits

Reviewing files that changed from the base of the PR and between 82c55ac and 9816c43.

📒 Files selected for processing (1)
  • content/deploy/edgeone.md
📝 Walkthrough

Walkthrough

Added a deployment documentation page for Nuxt applications on EdgeOne Pages. The page defines hosting metadata, documents the edgeone Nitro preset, explains console deployment with NITRO_PRESET=edgeone-pages, describes EdgeOne CLI requirements and behavior, and links to EdgeOne and Nitro deployment guides.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the addition of an EdgeOne Pages deployment guide.
Description check ✅ Passed The description explains the EdgeOne Pages documentation gap and summarizes the deployment guide content.
Linked Issues check ✅ Passed The PR adds the requested EdgeOne Pages deployment documentation and covers full-stack Nuxt deployment support.
Out of Scope Changes check ✅ Passed The documented changes align with the linked issue and stated objective; no unrelated changes are evident.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
content/deploy/edgeone.md (1)

22-28: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use the EdgeOne Makers deploy command.

The current EdgeOne CLI documentation recommends edgeone makers; edgeone pages is available only during the legacy transition. Update this example or mark it as the legacy equivalent.

Proposed fix
-edgeone pages deploy
+edgeone makers deploy
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/deploy/edgeone.md` around lines 22 - 28, Update the EdgeOne
deployment example in the documentation to use the current `edgeone makers`
deploy command instead of `edgeone pages deploy`. If retaining the existing
command, clearly label it as the legacy equivalent and document the Makers
command as the recommended path.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@content/deploy/edgeone.md`:
- Line 6: Update the nitroPreset frontmatter value in the EdgeOne deployment
guide from edgeone to edgeone-pages so it matches the NITRO_PRESET value used
later in the guide.

---

Nitpick comments:
In `@content/deploy/edgeone.md`:
- Around line 22-28: Update the EdgeOne deployment example in the documentation
to use the current `edgeone makers` deploy command instead of `edgeone pages
deploy`. If retaining the existing command, clearly label it as the legacy
equivalent and document the Makers command as the recommended path.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3bc89803-7bed-4a91-8ff1-32bb227a9233

📥 Commits

Reviewing files that changed from the base of the PR and between 29e59bb and 82c55ac.

⛔ Files ignored due to path filters (1)
  • public/assets/integrations/edgeone.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • content/deploy/edgeone.md

Comment thread content/deploy/edgeone.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Request to Add an EdgeOne Pages Deployment Documentation Page

1 participant