| Here are things I ran into. `wrangler login` doesn't work if I'm not already logged in to CloudFlare website. If I have to login first, it doesn't do whatever necessary redirect it should do so most of the time I have to run `wrangler login` twice. `wrangler dev` is slow. `wrangler dev` requires root domain. https://github.com/cloudflare/wrangler/issues/1529 I also feel that the interaction between DNS settings and workers is under-documented, probably because it crosses responsibility of two different teams. For example, it took me way too long to figure out that if I have a workers-only website for foo.bar.org, I have to put dummy DNS entry for foo.bar.org Frankly, despite reading wrangler docs multiple times, I don't think I fully understand the interactions between what's in the DNS, what's in the workers route and further more if you add pages to the mix. Docs should explicitly spell out DNS / routes setup for most common scenarios like: 1) workers-only site (no proxying to any other server) 2) workers in front of a proxied website Workers should be seamlessly integrated with pages i.e. pages should just automatically recognize and use workers-site/ directory on deploy. I don't think setting up pages automatically configures DNS settings for its domain, which it obviously should (might be mis-remembering). |
- > `wrangler login` doesn't work if I'm not already logged in to CloudFlare website This should be fixed in our last release!
- `wrangler dev` is slow. Agreed. We're working on making it faster, but miniflare is a great option for the fastest dev experience at the moment.
- Regarding DNS/domains/Workers, this is all great feedback. We should be making this more painless/intuitive. We'll work on it!