From a5636e995c8a5820382a69dede71758df1e7a354 Mon Sep 17 00:00:00 2001 From: Wes Johnson Date: Sat, 25 Feb 2023 17:19:49 -0500 Subject: [PATCH 1/4] chore(docs): add missing troubleshooting step --- docs/troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 5f26137..a507441 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -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. From be3051a8ef9df008602d63ba389a2ac1202c6796 Mon Sep 17 00:00:00 2001 From: Wes Johnson Date: Tue, 28 Feb 2023 09:52:36 -0500 Subject: [PATCH 2/4] address feedback --- docs/troubleshooting.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index a507441..78df708 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -14,8 +14,7 @@ If you attempted to deploy Wildebeest in your account and something failed, or y - Go to your account Workers / KV section and delete the `wildebeest-username-cache` and `wildebeest-terraform-username-state` namespaces. - 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 +- Go back to the [Getting Started](getting-started.md) readme and open the Deploy to Workers button link in an incognito tab (or a browser window with a cleared session/storage cache) - Delete your GitHub wildebeest forked repo. You can now start a clean install. @@ -43,16 +42,17 @@ If your zone is on Pro plan or above **and** you have deployed [WAF managed rule Block event example ![Block event example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/ea58f6e2-a320-4322-9b13-9f747f5e6300/public) + Depending on your existing setup, you can: - Lower OWASP ruleset's [sensitivity](https://developers.cloudflare.com/waf/managed-rules/reference/owasp-core-ruleset/#configure-in-the-dashboard) - [Skip](https://developers.cloudflare.com/waf/managed-rules/waf-exceptions/) (part of) managed rules, matching hostname `social.example` which path contains `/ap/users/` and `/inbox` -
- Skip rule example +
+ Skip rule example - ![Skip rule example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/96370b69-63c9-45a9-2b59-7267bf874c00/public) -
+ ![Skip rule example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/96370b69-63c9-45a9-2b59-7267bf874c00/public) +
[Index](../README.md) ┊ [Back](other-services.md) From efe37520963d45eb3668e76b361f9c5f6df03a0a Mon Sep 17 00:00:00 2001 From: Wes Johnson Date: Tue, 28 Feb 2023 09:53:40 -0500 Subject: [PATCH 3/4] revert whitespace changes --- docs/troubleshooting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 78df708..26d257e 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -49,10 +49,10 @@ Depending on your existing setup, you can: - Lower OWASP ruleset's [sensitivity](https://developers.cloudflare.com/waf/managed-rules/reference/owasp-core-ruleset/#configure-in-the-dashboard) - [Skip](https://developers.cloudflare.com/waf/managed-rules/waf-exceptions/) (part of) managed rules, matching hostname `social.example` which path contains `/ap/users/` and `/inbox` -
- Skip rule example +
+ Skip rule example - ![Skip rule example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/96370b69-63c9-45a9-2b59-7267bf874c00/public) -
+ ![Skip rule example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/96370b69-63c9-45a9-2b59-7267bf874c00/public) +
[Index](../README.md) ┊ [Back](other-services.md) From 197797b7c3ae582a4ff68140cb189372b4fa4b56 Mon Sep 17 00:00:00 2001 From: Wes Johnson Date: Tue, 28 Feb 2023 09:54:26 -0500 Subject: [PATCH 4/4] revert another --- docs/troubleshooting.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 26d257e..f3759e7 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -42,7 +42,6 @@ If your zone is on Pro plan or above **and** you have deployed [WAF managed rule Block event example ![Block event example screenshot](https://imagedelivery.net/NkfPDviynOyTAOI79ar_GQ/ea58f6e2-a320-4322-9b13-9f747f5e6300/public) - Depending on your existing setup, you can: