You can start the DO and call https://1.1.1.1/cdn-cgi/trace

G

GuillaumeLakanoOP•3/4/23, 5:10 PM

then you extract the colo information

G

GuillaumeLakanoOP•3/4/23, 5:10 PM

but in theory you should also got it from request.cf.colo, but for theses 2 solutions, you need to run the DO

G

GuillaumeLakanoOP•3/4/23, 5:12 PM

But if you want to known that from the generated ID, I suppose you can reverse the generated kind-of UUID, if I've understood well, the location is used in the generation of this id

GGuillaumeLakano You can start the DO and call https://1.1.1.1/cdn-cgi/trace

H

Hello, I’m Allie!•3/4/23, 5:13 PM

No, I got that, but I meant specifically the region the DO would be in, if I spawned it with

locationHint

locationHint

locationHint

locationHint. I can do a manually mapping from colos to regions, but iirc, they aren't 100% stable yet.

HHello, I’m Allie!No, I got that, but I meant *specifically* the region the DO would be in, if I s...

G

GuillaumeLakanoOP•3/4/23, 5:21 PM

Understood. Yep, as you said it's not stable, new DO will expands to new colos in the future. I suppose in the CF source code, there is a kind of mapping that match the closest "installed" colo. I don't known if this code is open, but could help... or do indeed a manual mapping, but this require to adjust it time to time...

MMisterNight hiyo, is it possible to add a (brand-new) DO to an existing pages project? I see...

L

Larry•3/5/23, 3:51 AM

They can be in the same repo because you have to deploy the DO separately from Pages anyway. I have a folder

./durable-objects

./durable-objects

./durable-objects

./durable-objects at the same level as

./functions

./functions

./functions

./functions in my repo. Put the wrangler.toml file for the Worker/DO in the

./durable-objects

./durable-objects

./durable-objects

./durable-objects folder and run

wrangler publish

wrangler publish

wrangler publish

wrangler publish from that folder whenever you update. I'm constantly forgetting that step and wondering why my smoke tests fail though so I keep promising myself I'm going to automate the publish as part of my Pages build but I have yet to do it.

B

Beny•3/5/23, 6:26 AM

Am I right with this calculation of a cost of $4.15 per month for a Durable Object to run 24/7?

86400 seconds x 128 MB = 11059200
11059200 / 1000 (1GB) = 11059.2
11059.2 x 30 (30 days) = 331776
331776 / 1000000 (million) = 0.331776
0.331776 x $12.50 = $4.1472

86400 seconds x 128 MB = 11059200
11059200 / 1000 (1GB) = 11059.2
11059.2 x 30 (30 days) = 331776
331776 / 1000000 (million) = 0.331776
0.331776 x $12.50 = $4.1472

86400 seconds x 128 MB = 11059200
11059200 / 1000 (1GB) = 11059.2
11059.2 x 30 (30 days) = 331776
331776 / 1000000 (million) = 0.331776
0.331776 x $12.50 = $4.1472

86400 seconds x 128 MB = 11059200
11059200 / 1000 (1GB) = 11059.2
11059.2 x 30 (30 days) = 331776
331776 / 1000000 (million) = 0.331776
0.331776 x $12.50 = $4.1472

MMisterNight since you can toss in regular workers

L

Larry•3/5/23, 2:17 PM

I didn't know you could "toss in regular workers" to Pages so my info may be outdated... unless you are referring to Pages advanced mode?

MMisterNight ah, even if they can be represented as migrations in the wranglers.toml it must ...

L

Larry•3/5/23, 3:23 PM

As far as I know wrangler.toml is ignored by Pages CI. I think I remember seeing somewhere that now

wrangler pages dev

wrangler pages dev

will pull from it though.

BBeny Am I right with this calculation of a cost of $4.15 per month for a Durable Obje...

H

Hello, I’m Allie!•3/5/23, 3:31 PM

For a single Durable Object, leaving it running 24/7 would make it fall under the "free" allotment of GB-S for Durable Objects.

BBeny Am I right with this calculation of a cost of $4.15 per month for a Durable Obje...

Z

zegevlier•3/5/23, 4:08 PM

That's very similar to what I came up with when I calculated it. But as HW said, running a single one for a month is included in the base paid tier

U

Unsmart•3/5/23, 6:59 PM

Pages are workers yeah but some features arent exposed through them. Pages is basically opinionated way to write and deploy workers so durable objects as part of a pages worker isnt exposed yet. Though you can bind to durable objects that other workers expose.

D

DanTheGoodman•3/6/23, 1:37 PM

I am trying to run a background promise to drain logs in a durable object that looks like this:

const res = new Response("broadcasted")
logger.Drain()
return res

const res = new Response("broadcasted")
logger.Drain()
return res

const res = new Response("broadcasted")
logger.Drain()
return res

const res = new Response("broadcasted")
logger.Drain()
return res

With

logger.Drain()

logger.Drain()

logger.Drain()

logger.Drain() looking like:

async (lines) => {
  console.log("draining logs!")
  await googleDestinationFunction(lines, c.env)
  console.log("done!")
}

async (lines) => {
  console.log("draining logs!")
  await googleDestinationFunction(lines, c.env)
  console.log("done!")
}

async (lines) => {
  console.log("draining logs!")
  await googleDestinationFunction(lines, c.env)
  console.log("done!")
}

async (lines) => {
  console.log("draining logs!")
  await googleDestinationFunction(lines, c.env)
  console.log("done!")
}

Looking at my execution logs within cloudflare, I see only the

draining logs!

draining logs!

draining logs!

draining logs! log, but not the

done!

done!

done!

done! log. I've also tried returning the

googleDestinationFunction

googleDestinationFunction

googleDestinationFunction

googleDestinationFunction log directly (which also contains logs that I do not see) and it just seems like the DO is exiting once the promise starts running... It is my understanding that the DO should let any other promises run the in background, correct?

MMisterNight answer: it has to have a worker, doesn't need a fetch handler, just has to exist

H

Hello, I’m Allie!•3/6/23, 5:17 PM

Note too that you can disable the

workers_dev

workers_dev

workers_dev

workers_dev route, so the Worker itself cannot incur any Requests.

MMisterNight where? in _routes.json?

H

Hello, I’m Allie!•3/6/23, 5:19 PM

No, in your

wrangler.toml

wrangler.toml

.

MMisterNight in this example, would it look like `export default {}` ? https://github.com/clo...

H

Hello, I’m Allie!•3/6/23, 5:20 PM

It might work with just the

export class MyDOClass

export class MyDOClass

export class MyDOClass

export class MyDOClass, but if it doesn't just add the

export default {}

export default {}

export default {}

export default {}.

MMisterNight do you have any suggestions for dev mode? should I be mocking out the worker int...

H

Hello, I’m Allie!•3/6/23, 5:22 PM

wrangler

wrangler

should be able to connect to a DO automatically. If you run

wrangler dev

wrangler dev

in your Worker, and then

wrangler pages dev dist --do BINDING=MyDOClass

wrangler pages dev dist --do BINDING=MyDOClass

wrangler pages dev dist --do BINDING=MyDOClass

wrangler pages dev dist --do BINDING=MyDOClass, they should be able to link together...

U

Unsmart•3/6/23, 5:25 PM

dont think it matters that much but do note that when you deploy a worker all DOs will reset all active connections to do a code update and might throw some errors for a second or so

MMisterNight `yarn wrangler pages dev ./dist --compatibility-date=2023-03-04 --do COUNTER=my_...

H

Hello, I’m Allie!•3/6/23, 6:18 PM

Try —do COUNTER=Counter@my_worker_name

You can start the DO and call https://1.1.1.1/cdn-cgi/trace

Similar Threads

Similar Threads

Similar Threads