GithubBackup/cloudflare_temp_email
1
0
Fork 0
mirror of https://github.com/dreamhunter2333/cloudflare_temp_email.git synced 2026-05-26 18:49:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify mailbox rebinding and page function actions (#1012)

Browse Source 
docs: clarify mailbox rebinding and page functions actions
This commit is contained in:
Dream Hunter
2026-04-29 01:53:35 +08:00
committed by GitHub
parent 7d68cbdffa
commit 4e01b4e26f
6 changed files with 26 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
vitepress-docs/docs/en/guide/actions/github-action.md
View File

@@ -57,6 +57,16 @@ Then go to the repository page `Settings` -> `Secrets and variables` -> `Actions
- If you need separate frontend and backend deployment that talks to Worker directly, find `Deploy Frontend` and click `Run workflow` to select a branch and deploy manually
- If you need Pages deployment with Page Functions forwarding backend requests, find `Deploy Frontend with page function` and click `Run workflow` to deploy manually
### Auto-Update with Page Functions Forwarding
If you want to use `Upstream Sync` for automatic updates and also let Pages forward backend requests through Page Functions, use the `Deploy Frontend with page function` workflow instead of `Deploy Frontend`.
- Enable `Upstream Sync`, `Deploy Backend`, and `Deploy Frontend with page function`
- Configure the `PAGE_TOML` repository secret by copying the content of `pages/wrangler.toml`
- Change the `service` field in `PAGE_TOML` to your Worker backend name
- This workflow runs `pnpm build:pages`, uses same-origin frontend requests, and does not read `FRONTEND_ENV`
- After each completed `Upstream Sync`, `Deploy Frontend with page function` deploys the frontend automatically when `PAGE_TOML` is configured
## How to Configure Auto-Update
1. Open the `Actions` page of the repository, find `Upstream Sync`, and click `enable workflow` to enable the `workflow`

2
vitepress-docs/docs/en/guide/common-issues.md
View File

@@ -10,6 +10,7 @@
| Sending emails to authenticated forwarding addresses using Cloudflare Workers | Use CF's API for sending, only supports recipient addresses bound to CF, i.e., CF EMAIL forwarding destination addresses |
| Binding multiple domains | Each domain needs to configure email forwarding to worker |
| Subdomain cannot receive email | Subdomains must have Email Routing **enabled separately** on Cloudflare with their own DNS records and Catch-all rule. Enabling it only on the apex domain does NOT cover subdomains. See [Email Routing](/en/guide/email-routing) |
| Recreating a previously used mailbox shows that the address already exists | The address may have been recreated or bound by another user after it expired or was unbound, so a normal user cannot reclaim it directly. If you have admin access, find the address in the admin address list, get its address credential, and then bind it to the target user again |
## Worker Related
@@ -59,3 +60,4 @@
| Issue | Solution |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| After Github Action deployment, CF always shows preview branch | Go to CF pages settings to confirm that the frontend branch matches the Github Action frontend deployment branch |
| Use GitHub Actions auto-update while forwarding backend requests through Page Functions | Enable the `Deploy Frontend with page function` workflow and configure the `PAGE_TOML` secret. Copy `pages/wrangler.toml` into `PAGE_TOML`, then change `service` to your Worker backend name. This workflow uses same-origin requests and does not need `FRONTEND_ENV` |