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
@@ -118,24 +135,43 @@ Upgrade to Pro for higher limits.
118
135
## Troubleshooting
119
136
120
137
**Build failures:**
138
+
121
139
- Check build logs in Cloudflare Dashboard
122
140
- Verify all environment variables are set
123
141
- Ensure `builder.config.ts` is correct
124
142
- Check storage credentials
125
143
126
144
**Missing photos:**
145
+
127
146
- Verify thumbnails and manifest are in build output
128
147
- Check file paths are correct
129
148
- Ensure storage is accessible during build
130
149
131
150
**Slow builds:**
151
+
132
152
- Use repo cache plugin to avoid full rebuilds
133
153
- Optimize storage access
134
154
- Consider reducing photo count
135
155
156
+
## Limitations
157
+
158
+
Deploying the `web` app directly to Cloudflare Pages results in a static site. This means you will lose server-side features provided by the `ssr` application (Next.js), such as:
159
+
160
+
-**Dynamic Open Graph (OG) Images**: Social media preview cards will not be generated dynamically.
161
+
162
+
-**Share/Iframe Support**: Specific sharing functionality that relies on server-side rendering may not work as expected.
163
+
164
+
To support these features on Cloudflare, you would need to deploy the `ssr` application using a Cloudflare Workers adapter for Next.js (e.g., `@opennextjs/cloudflare`), which adds significant complexity to the deployment process.
0 commit comments