Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(docs): add missing troubleshooting step #342

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ If you attempted to deploy Wildebeest in your account and something failed, or y
- Go to your account Workers / D1 and delete the `wildebeest-username` database.
- Launch [Zero Trust](https://one.dash.cloudflare.com/), select your account, go to Access / Applications and delete the `wildebeest-username` application.
- Go to https://deploy.workers.cloudflare.com/, open the site settings in your browser and delete all the cookies and local storage data.
- If you aren't prompted to fill any of the fields for admin email address, your domain name, instance title, etc., you'll need to add these values to the Actions Variables UI for your newly forked repo (`https://github.com/YOURUSERNAME/wildebeest/settings/variables/actions`): `ADMIN_EMAIL`, `CF_DEPLOY_DOMAIN`, `CF_ZONE_ID`, `INSTANCE_TITLE`, and `INSTANCE_DESCR`. You can re-run any action that failed on account of those values being missing once they are filled
- Delete your GitHub wildebeest forked repo.

You can now start a clean install.
Expand Down