b337a44e62
- Add daily request limit per IP in blacklist settings (1-1,000,000/day) - Refactor access control logic: merge blacklist and rate limit checks - Remove RATE_LIMIT_API_DAILY_REQUESTS env var, use database config instead - Move x-custom-auth check earlier in middleware chain - Add comprehensive English documentation (31 new guide pages) - Improve code structure and error handling 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>
1.4 KiB
Cloudflare Pages Frontend
[!warning] Notice Choose one of the following methods
Deploy Worker with Frontend Assets
Refer to Deploy Worker
Separate Frontend and Backend Deployment
The first deployment will prompt you to create a project. For the production branch, enter production.
cd frontend
pnpm install
cp .env.example .env.prod
Modify the .env.prod file.
Change VITE_API_BASE to the worker url created in the previous step. Do not add / at the end.
For example: VITE_API_BASE=https://xxx.xxx.workers.dev
pnpm build --emptyOutDir
# The first deployment will prompt you to create a project, for production branch enter production
pnpm run deploy
After deployment, you can see your project in the Cloudflare console. You can configure a custom domain for pages.
Forward Backend Requests Through Page Functions
Forwarding requests from page functions to the worker backend can achieve faster response times.
The first deployment will prompt you to create a project. For the production branch, enter production.
If your worker backend name is not cloudflare_temp_email, please modify pages/wrangler.toml.
cd frontend
pnpm install
# If you want to enable Cloudflare Zero Trust, you need to use pnpm build:pages:nopwa to disable caching
pnpm build:pages
cd ../pages
pnpm run deploy