Variable ADMIN_DEPLOY_HTMLConst
ADMIN_DEPLOY_HTML: "<h1>Deploy</h1>\n<div class=\"card bad\"><p><strong>There is no one-click deploy yet, and this page will not pretend otherwise.</strong>\nNo provisioning exists in this repository: no account picker and no namespace creation. A button here that appeared to work would be worse than no button, so what follows is the requirement a provisioner has to satisfy. Credentials are the one step that is now covered, below.</p></div>\n<h2>Connect a Cloudflare Account</h2>\n<p class=\"sub\">Two ways in. Pasting an account ID and API token still works and needs no setup. OAuth issues a short-lived scoped grant instead, revocable from your Cloudflare dashboard, and drupflare never stores a long-lived secret.</p>\n<div class=\"card\"><p><strong>OAuth needs a client you register once.</strong> Cloudflare registers a redirect URI against the client, and every drupflare deployment answers on a different origin, so there is no shared client that could work for all of them. In your dashboard go to <em>Manage account › OAuth clients</em>, create one with <strong>private</strong> visibility, and register this callback:</p>\n<pre style=\"margin:0;overflow-x:auto\"><code>__CFW_CALLBACK__</code></pre>\n<p class=\"sub\">Private visibility is enough: you are a member of the account you are authorising. Then paste the client ID here. The client ID is not a secret, but it is stored in this site's own database rather than in KV, because a KV writer who could change it could point the consent screen at an application they control.</p>\n<form id=\"cfoauth\"><label>Client ID<input name=\"client_id\" autocomplete=\"off\" spellcheck=\"false\" value=\"__CFW_CLIENT_ID__\"></label>\n<button type=\"submit\">Connect With Cloudflare</button></form>\n<p id=\"cfoauth-out\" class=\"sub\">__CFW_NOTICE__</p></div>\n__CFW_CONNECTED__\n<script>\n__CFW_CONNECT_SCRIPT__\n</script>\n<h2>What deploying actually involves</h2>\n<table><thead><tr><th>Step</th><th>Detail</th><th>Can it be scripted?</th></tr></thead><tbody>__CFW_ROWS__</tbody></table>\n<h2>What works today</h2>\n<p class=\"sub\">From a checkout, with wrangler authenticated against your own account:</p>\n<div class=\"card\"><pre style=\"margin:0;overflow-x:auto\"><code>bun run deploy</code></pre></div>\n<p class=\"sub\">That is the tax this page exists to remove: it needs a terminal, a checkout, and an account already configured. Until the two <em>needs a human</em> steps above have a flow, the button stays absent.</p>\n"