Skip to content

Add docs for wrangler dev + tunnels#28228

Closed
ask-bonk[bot] wants to merge 7 commits into
productionfrom
opencode/issue28227-20260209234637
Closed

Add docs for wrangler dev + tunnels#28228
ask-bonk[bot] wants to merge 7 commits into
productionfrom
opencode/issue28227-20260209234637

Conversation

@ask-bonk

@ask-bonk ask-bonk Bot commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

All tasks are complete. Here is a summary of the changes:

Summary of changes

New file

  • src/content/docs/workers/development-testing/expose-dev-server.mdx — New how-to page that walks through exposing a wrangler dev or vite dev session using Cloudflare Tunnel. Covers:
    • How the tunnel architecture works
    • Quick tunnels (no account required) with tabbed package manager examples
    • Named tunnels with persistent hostnames
    • Configuration details: port matching, interface binding, local vs remote mode, Vite custom ports
    • Common use cases table
    • Limitations

Edited files

  • src/content/docs/workers/development-testing/index.mdx (line 53) — Added a cross-link sentence after the "Get started" links in the Local development section: "To share your dev server with others or receive external webhooks, refer to Expose your dev server."

  • src/content/docs/cloudflare-one/.../trycloudflare.mdx (line 34) — Added a Workers-specific use case to the FAQ: exposing a local Workers dev server with cloudflared tunnel --url http://localhost:8787.

  • src/content/docs/workers/wrangler/commands.mdx (line 199) — Added a note under the --port flag description referencing the tunnel guide for port matching.

Validation

  • npm run check passed with 0 errors (frontmatter schemas, content collections, and Astro types all valid).

Closes #28227

github run

Co-authored-by: irvinebroque <irvinebroque@users.noreply.github.com>
@github-actions

github-actions Bot commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/ @nikitacano, @ranbel, @cloudflare/pcx-technical-writing
/src/content/docs/workers/ @cloudflare/workers-docs, @GregBrimble, @irvinebroque, @mikenomitch, @korinne, @WalshyDev, @cloudflare/deploy-config, @cloudflare/pcx-technical-writing, @cloudflare/wrangler, @mattietk, @cloudflare/dev-plat-leads

@irvinebroque

Copy link
Copy Markdown
Contributor

/bonk please work on these edits

  • don't say "edge"
  • remove the guidance that says "Do not use --remote, which uploads your code to the Cloudflare network and defeats the purpose of a tunnel to your local server." - this is not helpful
  • remove "Tunnel latency adds round-trip time to every request. This is acceptable for development but is not representative of production performance."

Comment thread src/content/docs/workers/wrangler/commands.mdx Outdated
@irvinebroque

Copy link
Copy Markdown
Contributor

/bonk fix Invalid link: /cloudflare-one/applications/configure-apps/self-hosted-public-app/ (found twice in one file).

@ask-bonk

This comment was marked as outdated.

@ask-bonk

ask-bonk Bot commented Feb 10, 2026

Copy link
Copy Markdown
Contributor Author

Bonk workflow failed. Check the logs for details.

View workflow run

Co-authored-by: irvinebroque <irvinebroque@users.noreply.github.com>
@ask-bonk

ask-bonk Bot commented Feb 10, 2026

Copy link
Copy Markdown
Contributor Author

Fixed both occurrences in src/content/docs/workers/development-testing/expose-dev-server.mdx:

  • Line 141: /cloudflare-one/applications/configure-apps/self-hosted-public-app//cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/
  • Line 196: Same replacement in the use cases table

The correct path matches the 44 other references to this page across the codebase.

github run

Comment thread src/content/docs/workers/development-testing/expose-dev-server.mdx
### Start your dev server

<Tabs>
<TabItem label="npm">

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.

Isn't there a component that automatically provides the different package manager options?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

/bonk use the PackageManager component

@ask-bonk

ask-bonk Bot commented Feb 10, 2026

Copy link
Copy Markdown
Contributor Author

Changes made to src/content/docs/workers/development-testing/expose-dev-server.mdx:

  1. Replaced manual Tabs/TabItem block with PackageManagers component (lines 33-37) — Uses <PackageManagers type="exec" pkg="wrangler" args="dev" /> and <PackageManagers type="exec" pkg="vite" args="dev" />, matching the pattern used on the parent development-testing/index.mdx page.

  2. Also addressed the remaining review comments from @irvinebroque:

    • Removed "at the Cloudflare edge" (line 20)
    • Removed the "Local mode vs remote mode" section with the --remote guidance
    • Removed the tunnel latency limitation bullet

github run

Address reviewer feedback to show dashboard-managed tunnels as the
recommended approach alongside the CLI-based local configuration,
using tabs to present both options concisely.
@ask-bonk

ask-bonk Bot commented Feb 10, 2026

Copy link
Copy Markdown
Contributor Author

Done. Here's what I changed in src/content/docs/workers/development-testing/expose-dev-server.mdx:

Rewrote the "Named tunnel (persistent hostname)" section to address @nikitacano's and @irvinebroque's feedback:

  • Added Tabs/TabItem components to present two approaches side by side:

    • Dashboard (Recommended) — A concise 5-step walkthrough for creating a remotely-managed tunnel via the Cloudflare One dashboard, with a link to the full Create a tunnel (dashboard) docs.
    • CLI — The existing local configuration approach (cloudflared tunnel login/create, config.yml, cloudflared tunnel run), preserved as-is.
  • The intro paragraph now explicitly notes that the dashboard approach is recommended.

  • The "Restrict access" subsection remains shared across both approaches.

github run

@elithrar

Copy link
Copy Markdown
Collaborator

/bonk update this PR: focus on the account level tunnel experience in https://developers.cloudflare.com/changelog/2026-02-20-tunnel-core-dashboard/ (follow the links in the changelog for guidance).

…orking > Tunnels)

Per the 2026-02-20 changelog, Tunnel management for public applications
is now available in the main Cloudflare Dashboard. Update the recommended
dashboard flow to use Networking > Tunnels instead of the Cloudflare One
dashboard.
@ask-bonk

ask-bonk Bot commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

Done. Here is a summary of the change:

File changed: src/content/docs/workers/development-testing/expose-dev-server.mdx

What changed in the Dashboard (Recommended) tab:

  • Before: Directed users to log in to Cloudflare One and go to Networks > Connectors > Cloudflare Tunnels
  • After: Directs users to log in to the Cloudflare dashboard and go to Networking > Tunnels

This aligns with the 2026-02-20 changelog which announces that Tunnel management for public applications is now available in the main (Core) Cloudflare Dashboard. The changelog explicitly states the Core Dashboard at Networking > Tunnels is the right place for "securing origin servers and public applications" — which is exactly the use case of exposing a dev server via tunnel.

github run


## Limitations

- Quick tunnels generate a new URL each time you restart `cloudflared`. For stable URLs, use a named tunnel.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

/bonk things like "use a named tunnel" should be links for what / how to do that. re-review with that in mind + fix.

@ask-bonk

ask-bonk Bot commented Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

Done. Here is a summary of the changes in src/content/docs/workers/development-testing/expose-dev-server.mdx:

Added links to all previously-unlinked concept references:

  • Line 65: cloudflared CLI now links to the downloads page
  • Line 160: "Cloudflare Vite plugin" now links to /workers/vite-plugin/ (was linked earlier in the page but not in this section)
  • Lines 180-183 (Common use cases table): All "Quick tunnel" references now link to #quick-tunnel-no-account-required, all "named tunnel" references link to #named-tunnel-persistent-hostname
  • Line 187: "Quick tunnels" now links to the trycloudflare docs, "named tunnel" links to #named-tunnel-persistent-hostname
  • Line 190: "named tunnel" now links to #named-tunnel-persistent-hostname

github run

@github-actions

github-actions Bot commented Mar 7, 2026

Copy link
Copy Markdown
Contributor

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).

@github-actions github-actions Bot added the stale label Mar 7, 2026
@github-actions

github-actions Bot commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

Hey there, we've closed out this pull request because it's been stale for a while and there's been no additional action on it. If these changes are still relevant, open a new pull request (or flag to us in a GitHub issue).

@github-actions github-actions Bot closed this Apr 6, 2026
@github-actions
github-actions Bot deleted the opencode/issue28227-20260209234637 branch April 22, 2026 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add docs for how to use wrangler dev with cloudflare tunnels

10 participants