You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally launched as an email spam tracker, Cloudflare today offers extensive capabilities for users to register, manage domains as a registrar, and monitor, secure, and configure an entire IT infrastructure.
@@ -73,7 +74,7 @@ Before proceeding, you will need two details and one DNS configuration from Clou
73
74
- Return to your domain’s home page (the **Overview** page should still be open) and click on **DNS** on the left sidebar.
74
75
- Click **Add record** on the _Records_ page and enter the following details:
75
76
76
-

77
+

77
78
78
79
<details>
79
80
<summary>Click to view DNS record details</summary>
@@ -133,7 +134,7 @@ Details for each input after clicking **Add Integration** under **Cloudflare**:
133
134
134
135
### Testing Cloudflare Integration
135
136
136
-
Visit our [recipes](/recipes) to test an application. Your next deployment should use your designated domain! (If not, [talk to us on Discord](https://zephyr-cloud.io/discord)).
137
+
Your next deployment should use your designated domain! (If not, [talk to us on Discord](https://zephyr-cloud.io/discord)).
137
138
138
139
When using our managed cloud (Cloudflare) or custom Cloudflare integration, avoid including capital letters in names for `package.json`, module federation configuration, or assets to prevent issues with Cloudflare queries.
139
140
@@ -180,7 +181,7 @@ In your Cloudflare dashboard, navigate to **Workers & Pages** and then **KV** to
180
181
-`ze_envs`: stores application environment and access rights.
181
182
-`ze_snapshot`: stores application snapshots compared against the previous build.
182
183
- If deploying an application previously on our managed cloud, run `rm -rf ~/.zephyr` before deployment.
183
-
- If you encounter issues deploying Micro-frontend applications, see our [Micro-frontend deployment guide](/how-to/mf-guide).
184
+
- If you encounter issues deploying Micro-frontend applications, refer to our deployment documentation.
@@ -202,7 +202,7 @@ Make every repository deployed through Zephyr attempt to deploy through this
202
202
203
203
### How to test it
204
204
205
-
Navigate to our [recipes](/recipes) to try one of the application, you should see your next deployment deployed through your designated domain! (if not come [talk to us](https://zephyr-cloud.io/discord))
205
+
Navigate to our recipes to try one of the application, you should see your next deployment deployed through your designated domain! (if not come [talk to us](https://zephyr-cloud.io/discord))
206
206
207
207
208
208
</Steps>
@@ -247,7 +247,6 @@ Sign in to your Netlify team's main dashboard page and select your site project,
247
247
-`site:ze_envs` stores you application's environment, access right etc.
248
248
-`site:ze_snapshot` stores your application's snapshots comparing against previous build.
249
249
- If you are deploying an application that's previously deployed through our managed cloud, you will need to run `rm -rf ~/.zephyr` before deployment.
250
-
- If you faced issues while deploying Micro-frontend application, you can follow your complete guide on [how to deploy Micro-frontend applications on Zephyr](/how-to/mf-guide).
0 commit comments