Verifying you are human. This may take a few seconds.
Verifying you are human. This may take a few seconds.
it returns an errorwhat is the error?
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).pages_build_output_dir in wrangler.toml is resolving to a path thats outside the output directory, please check your configuration/main to main?Error: Output directory "main" not found.Cloudflare Pages is for static content (HTML, CSS, JS, images and other such files). It will not run a webserver such as Express, Koa or the likes. If you're using those to serve static content then you can just remove that part and use Pages!
If you're doing more dynamic content you can use Functions (https://developers.cloudflare.com/pages/platform/functions). It will run code on request (so still not a webserver in the conventional sense). This would allow for more dynamic content though especially with KV (Key Value storage) and Durable Objects (transactional data storage). Functions are natively integrated with Pages so are super easy to get up and running along your website.
Otherwise, a good old VPS or dedicated server from one of the many hosts out there is for you.
./ with no custom root directory set, you have an index.html at rootpages_build_output_dir = ""for root dir, slightly cleaner
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_IDa398d794-7322-4c97-96d9-40b5140a8d9bpages_build_output_dir/mainError: Output directory "main" not found../