Cloudflare Developers•3y ago

Where did you see that it's Enterprise only?

Kkian Where did you see that it's Enterprise only?

李

李二牛li2niu•4/13/23, 4:43 AM

https://community.cloudflare.com/t/starting-with-workers-and-lat-long/217639

Cloudflare Community

Starting with workers and Lat/Long

Just started using Cloudflare and liking the testing that we are doing. We are working to get Latitude and Longitude into the header similar to how we are doing that with a competing CDN. I have been reading the articles below and having some issues just getting started with workers and the general setup. Any assistance would be appreciated.

李

李二牛li2niu•4/13/23, 4:43 AM

Keep in mind that the event.cf object and its properties, including event.cf.latitude, are only available to Cloudflare Enterprise customers in the scope of their workers running on the Cloudflare network.

李

李二牛li2niu•4/13/23, 4:44 AM

In the first thread, the last user said that.

李李二牛li2niu Keep in mind that the event.cf object and its properties, including event.cf.lat...

李

李二牛li2niu•4/13/23, 4:44 AM

It is said by GPT4

李

李二牛li2niu•4/13/23, 4:45 AM

{
"outcome": "exception",
"scriptName": "wapi",
"exceptions": [
{
"name": "TypeError",
"message": "Cannot read properties of undefined (reading '0')",
"timestamp": 1681312866750
}
],
"logs": [
{
"message": [
{
"code": "404"
}
],
"level": "log",
"timestamp": 1681312866750
}
],
"eventTimestamp": 1681312865895,
"event": {
"request": {
"url": "https://wapi.li2niu.com/v1?sign=REDACTED&provider=q&lang=8389372&api_key=&lat=-0.00&lon=0.00",
"method": "GET",
"headers": {
"accept": "/",
"accept-encoding": "gzip",
"accept-language": "zh-CN,zh-Hans;q=0.9",
"cache-control": "no-cache",
"cf-connecting-ip": "114.92.92.54",
"cf-ipcountry": "CN",
"cf-ray": "7b6c7503c9724136",
"cf-visitor": "{"scheme":"https"}",
"connection": "Keep-Alive",
"content-type": "application/x-www-form-urlencoded",
"host": "wapi.li2niu.com",
"user-agent": "ConnectMobile/4 CFNetwork/1404.0.5 Darwin/22.3.0",
"x-forwarded-proto": "https",
"x-real-ip": "114.92.92.54"
},
"cf": {
"clientTcpRtt": 242,
"longitude": "121.45810",
"latitude": "31.22220",
"tlsCipher": "AEAD-AES128-GCM-SHA256",
"continent": "AS",
"asn": 4812,
"clientAcceptEncoding": "gzip, deflate, br",
This is a json from worker log. I saw the lat and lon in event.cf

kianOP•4/13/23, 4:49 AM

It is said by GPT4

Ignore GPT-4 then

kianOP•4/13/23, 4:50 AM

It'll work fine regardless of plan

sirhype•4/13/23, 4:54 AM

By chance, does anyone have a sample Worker that has separate environments (staging/prod) with different endpoints and different environment variables for each?

I want to setup a staging API for my Worker that deploys to staging.example.com/api/v1 and uses separate environment variables (beta DB)

kianOP•4/13/23, 5:32 AM

# Top-level configuration
name = "my-worker"
main = "src/index.js"
compatibility_date = "2022-07-12"

workers_dev = false
route = { pattern = "example.org/*", zone_name = "example.org" }

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

[env.staging]
name = "my-worker-staging"
route = { pattern = "staging.example.org/*", zone_name = "example.org" }

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<STAGING_KV_ID>" }
]

# Top-level configuration
name = "my-worker"
main = "src/index.js"
compatibility_date = "2022-07-12"

workers_dev = false
route = { pattern = "example.org/*", zone_name = "example.org" }

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

[env.staging]
name = "my-worker-staging"
route = { pattern = "staging.example.org/*", zone_name = "example.org" }

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<STAGING_KV_ID>" }
]

kianOP•4/13/23, 5:33 AM

Just add it under a [env.foo] header

DDio guys are trying to use service binding. There are 2 worker A "user" and a "pars...

Dio•4/13/23, 5:45 AM

inside worker there is access to service binding, but not inside DO. How can this be solved? Workers work locally

kianOP•4/13/23, 8:15 AM

The only concept that applies to Workers is accounts - so yeah, you could use other accounts but I wouldn't personally

kianOP•4/13/23, 8:15 AM

I also don't use enough Workers for organisation to be an issue so take that with a grain of salt

kianOP•4/13/23, 8:22 AM

Not particularly, I just rely on Git/Wrangler to manage all of my projects

kianOP•4/13/23, 10:01 AM

You don't - that's just how Workers work.

kianOP•4/13/23, 10:01 AM

When they receive a request, the Worker will be invoked in the colo that the user hit.

00xxxxx If I want every deployment worker to execute my code, is there a way to do it? I...

Hello, I’m Allie!•4/13/23, 10:04 AM

Workers only spawn when processing a Request, and then they are evicted, so that wouldn't really do much

Hello, I’m Allie!•4/13/23, 10:04 AM

So each request may be processed by a new Worker

00xxxxx Is it possible to trigger a request when deploying?

Hello, I’m Allie!•4/13/23, 10:06 AM

I guess? But it would only run in that one Worker

Hello, I’m Allie!•4/13/23, 10:07 AM

Workers aren't containers that stay on until they are shut down

Hello, I’m Allie!•4/13/23, 10:07 AM

They only exist as long as they are needed, and then they are scaled to zero. And there is no way to directly interact with a specific one

00xxxxx When deploying, did you just copy the code to the server? Is it possible to also...

Hello, I’m Allie!•4/13/23, 10:10 AM

What are you trying to do? I'm not following.

Kkian ```toml # Top-level configuration name = "my-worker" main = "src/index.js" comp...

sirhype•4/13/23, 10:10 AM

Can't seem to do it this way with custom staging env variables (like using a staging.env file)

kianOP•4/13/23, 10:11 AM

.env.env files aren't considered by Workers (Wrangler) at all

sirhype•4/13/23, 10:11 AM

Ah, it's a Miniflare thing?

sirhype•4/13/23, 10:11 AM

.dev.vars is a Wrangler thing right?

Ssirhype .dev.vars is a Wrangler thing right?

Hello, I’m Allie!•4/13/23, 10:12 AM

Yup

00xxxxx I want to visit a website once from all over the world and see the latency in ea...

Hello, I’m Allie!•4/13/23, 10:13 AM

You might be able to build something like that with Durable Objects(which you can only lock to regions, and not individual datacenters), or hit a Worker with a ping from every Datacenter, but that requires the Enterprise plan.

sirhype•4/13/23, 10:17 AM

wait i'm dumb please ignore me lul

sirhype•4/13/23, 10:17 AM

I can just make a new env, it'll have its own secrets in wrangler. Then I use .dev.vars for that environment locally. and prod will use the prod secrets

sirhype•4/13/23, 10:18 AM

I was overthinking it

00xxxxx Yes, I want to ping the address of a certain website in each data center, and th...

Hello, I’m Allie!•4/13/23, 10:22 AM

Yes, but this requires Enterprise to achieve, which costs a few thousand $ a month.

Hello, I’m Allie!•4/13/23, 10:22 AM

This being a Load Balancer Health Check

00xxxxx Yes, the principle is similar to that of loadbalancer. Is there any ready-made s...

Hello, I’m Allie!•4/13/23, 10:28 AM

https://developers.cloudflare.com/load-balancing/understand-basics/monitors

Monitors · Cloudflare Load Balancing docs

Balance traffic loads, manage failovers, monitor server and pool health, and apply geographic control with Cloudflare Load Balancing

bret_pat•4/13/23, 9:51 PM

Can a bundled worker know it's CPU usage? I have a task that consists of a long series of API calls and wanted to know when it would be time to kick-off the next bundled service worker.

Bbret_pat Can a bundled worker know it's CPU usage? I have a task that consists of a long ...

Hello, I’m Allie!•4/13/23, 9:55 PM

It cannot

SSanju Hi everyone, how to use workers cron to trigger certain endpoint?. For example -...

chientrm.com•4/14/23, 4:42 AM

use fetchfetch?

# Top-level configuration name = "my-worker" main = "src/index.js" compatibility_date = "2022-07-12" workers_dev = false route = { pattern = "example.org/*", zone_name = "example.org" } kv_namespaces = [ { binding = "<MY_NAMESPACE>", id = "<KV_ID>" } ] [env.staging] name = "my-worker-staging" route = { pattern = "staging.example.org/*", zone_name = "example.org" } kv_namespaces = [ { binding = "<MY_NAMESPACE>", id = "<STAGING_KV_ID>" } ]

Where did you see that it's Enterprise only?

Similar Threads

Similar Threads

Similar Threads