GithubBackup/cloudflare_temp_email
1
0
Fork 0
mirror of https://github.com/dreamhunter2333/cloudflare_temp_email.git synced 2026-06-09 01:20:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: improve deployment troubleshooting (#1011)

Browse Source 
* docs: improve deployment troubleshooting docs

* docs: fix GitHub casing in FAQ

* docs: clarify subdomain address creation
This commit is contained in:
Dream Hunter
2026-04-29 01:36:59 +08:00
committed by GitHub
parent 6d43c107d8
commit 7d68cbdffa
18 changed files with 153 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
vitepress-docs/docs/en/guide/quick-start.md
View File

@@ -30,6 +30,13 @@ Then review all changes from your current version onwards. Note that `Breaking C
Then refer to the documentation below to use `CLI` or `UI` to redeploy the `worker` and `pages` over the previous deployment.
Upgrading does not mean editing the old code already running in the Cloudflare console. It means redeploying the new version artifacts over the existing Worker and Pages deployment:
- If you use UI deployment, download the latest release `worker.js` and `frontend.zip`, then upload them again using the same deployment method.
- If you use GitHub Actions, sync your fork first and rerun the corresponding workflow.
- If the changelog lists database changes, run the upgrade in `Admin -> Quick Setup -> Database`, or execute the corresponding SQL according to the D1 guide.
- If the frontend still shows an old error after upgrading, test in an incognito window or clear browser cache so it stops loading the old frontend assets.
### CLI Deployment
- [Update D1 via Command Line](/en/guide/cli/d1)