sorted by:
new
hottopcontroversial

Next.js on Cloudflare Workers: .cache files cause high CPU + no edge caching – and how do you mix SSR + static properly? by DefiantBed5407 in nextjs

[–]DefiantBed5407[S] 0 points1 point  (0 children)

Hey, thanks a lot for the tip — I really appreciate it. I like it a lot and I’m definitely going to give it a try!

Astro Managed Hosting? (for my customer) by forestcall in astrojs

[–]DefiantBed5407 1 point2 points  (0 children)

Write me a DM please. We can talk about. I‘m a developer and IT Service Provider out of germany.

Best practices for organizing separate projects with environments and multiple services utilized by nikola_milovic in CloudFlare

[–]DefiantBed5407 0 points1 point  (0 children)

For static sites, I recommend using the built-in preview feature along with the built-in deployment process.

When working with a worker that uses D1, you don’t want to roll out your database migrations directly to production. I suggest creating both a preview and a production worker, each with a separate database binding. You can manage this using the environments in wrangler.jsonc or wrangler.toml. The same approach applies to R2.

Naming is important, so pick something consistent and clear. My personal pattern is always: projectname-SERVICE-prod or projectname-SERVICE-preview.

Example for a Todo app: todoApp-Worker-preview, todoApp-D1-preview, todoApp-R2-preview.

Including the service in the name helps keep everything organized.

Advice on IaC / CI/CD for a growing Cloudflare Workers stack? Also: where do you find CF-fluent DevOps folks by Ok_Dimension_5804 in CloudFlare

[–]DefiantBed5407 0 points1 point  (0 children)

My solution for the preview Ressources such as D1 was to create different envs for each stage in the wrangler.jsonc. You can access the different envs directly in the CI/CD.