The database connector connects to a WebSocket, which would be provided by the Tunnel. If you are co

The database connector connects to a WebSocket, which would be provided by the Tunnel. If you are connecting to a public DB that doesn't provide a WebSocket API, then it will not work.

HHello, I’m Allie!The database connector connects to a WebSocket, which would be provided by the T...

Tarnadas•4/12/23, 8:30 PM

Are there any other libraries I could use instead, so that I don't need the tunnel?

Tarnadas•4/12/23, 8:32 PM

Will go to sleep now so checking back later

TTarnadas Are there any other libraries I could use instead, so that I don't need the tunn...

Hello, I’m Allie!OP•4/12/23, 8:33 PM

No. At the moment, unless you have access to the TCP Worker beta, then you cannot connect to anything that doesn't support HTTP(S) or WebSockets, whether that be a Database, a Live Stream, or something else.

Hello, I’m Allie!OP•4/12/23, 8:34 PM

Note too that directly opening a connection to your DB in a Worker may not be the best approach anyway, as most databases are not optimized for extremely short-lived connections running only 1-2 queries.

JJorgeDev Does anyone know if it is possible to run workers on only one region?

Cyb3r-Jak3•4/12/23, 9:56 PM

Not without being enterprise. You can just make a firewall that blocks access to the worker apart from certain areas depending on your needs

addison•4/12/23, 10:27 PM

If I need to cache posts a user loads from the db should I be using workers kv for this?

SSilence Does anyone host a discord bot on pages/functions? If so could you tell me do yo...

Cyb3r-Jak3•4/13/23, 1:08 AM

You should probably do it during the deployment process

Chaika•4/13/23, 3:30 AM

Cloudflare Apps are pretty much abandoned/unmaintained at this point. Most of them are by third party devs as well, it might be that the ones you are using are broken
This channel is for workers, if you want to talk about Apps more, please use #general-discussions

Dio•4/13/23, 3:48 AM

guys are trying to use service binding. There are 2 worker
A "user" and a "parser".
I've written service binding in "parser "config. I run -local 2 worker . I try to get it via env.user, but I see there is no «user» in parser env, although at start it says that there is service binding in console

李

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

Hi, all , I saw event.cf.longitude is only available for Enterprise customers, so it means we 5$ paid plan users cannot access that? Thanks for your responding

kian•4/13/23, 4:37 AM

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

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

It is said by GPT4

Ignore GPT-4 then

kian•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)

kian•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>" }
]

kian•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

kian•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

kian•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

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

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

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

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

kian•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!OP•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!OP•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!OP•4/13/23, 10:06 AM

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

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

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

Hello, I’m Allie!OP•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!OP•4/13/23, 10:10 AM

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

# 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>" } ]

The database connector connects to a WebSocket, which would be provided by the Tunnel. If you are co

Similar Threads

Similar Threads

Similar Threads