Hello everyone,
I am currently following this tutorial at https://developers.cloudflare.com/workers/platform/environments. As part of the tutorial, I have set up three separate workers for development, staging, and production environments. However, when I view them in the Cloudflare UI, all three workers are labeled as "production" and display a note indicating "1 environment". I am unsure why this is the case, and I would appreciate any explanation of this behavior. Thank you.
#Confused about Environments
4 messages · Page 1 of 1 (latest)
What you're seeing is expected behaviour. It's a little confusing since the dash environments and wrangler ones are completely different, and the dash ones are currently disabled. Someone had a similar question recently and I summarised at https://community.cloudflare.com/t/environments-vs-deployments/451036/2?u=cherryjimbo 🙂
Cloudflare Community
The terminology around this all is a little confusing, sorry. Let me see if I can summarise. Originally, Cloudflare introduced Service Environments. These allowed users to create environments in the dash, and split config between them. This had issues and was “temporarily” disabled. All the time during this, Wrangler offered its own version of...
Thank you James! Can I have additional question? Is there any commonly used CI/CD service for workers? Thinking about something like https://seed.run/ for AWS or Heroku Pipelines https://devcenter.heroku.com/articles/pipelines
I personally use GitHub Actions, and Cloudflare has first party support with https://github.com/cloudflare/wrangler-action. But any CI will work great honestly since it’s all standard tooling available on npm