Disabling GitHub CI deployments shouldn’t disable the domain. Do you see any deployments to the main
Disabling GitHub CI deployments shouldn’t disable the domain. Do you see any deployments to the main branch?
LI use master
HThe subdomain on Pages is based on the branch you are on. If you don’t have a main branch, you won’t have a main subdomain
Lah!
Lbut it doesn't show me any URL with master subdomain
HCan you screenshot the deployments?
LI'm on phone right now, but I just tried the URL:
master.<project>.pages.dev doesn't work, only main.<project>.pages.dev but that shows an old outdated deployment, not the latest!
and I never had a main branch btw
master.<project>.pages.dev doesn't work, only main.<project>.pages.dev but that shows an old outdated deployment, not the latest!
and I never had a main branch btw
Pits possible to write into Durable Object from external server by API?
HYes, but the call still has to go through a Worker
Pthank you, how long take DO read and write, i know there are many factors, byt typically
HFrom the external API, or within the DO?
Pfrom worker
HThat would be dependent on where the DO is. If it is nearby, I’d say ~10-20 ms
Pand if its not nearby? 
L
L(btw, I don't have a main branch, only master and dev)
Lneither of the domains listed there work
H+200 ms
HThough that is rare
HMostly Australia
HThat’s because production doesn’t have a valid deployment
Pthats totally ok for my case if its rarely ~200ms, thank you
LAh!
I just set the env var with wrangler and tried to deploy again but it failed again with, even though the env var is present in the worker named
I just set the env var with wrangler and tried to deploy again but it failed again with, even though the env var is present in the worker named
t4-api:
HOh wait… it probably expects a global. What happens if you initialize it as it asks, in the constructor?
Lbtw, this constructor would otherwise read the same env var if I didn't pass this:
HAfaik, process.env is only defined within Next
HAt least on Workers
Lwhat do you mean by that?
Lthis project uses next.js
HWorkers don’t have global env variables. Next gets around this somehow, but afaik that only applies within the Next scope
HSo a 3rd-party package wouldn’t be able to read any variables
Lwhat's the Next scope?
HThe code you write with Next
Lbut the way I'm reading from process.env and passing it to the constructor should work, right?
HYes. Just to be sure, check whether they are defined, by console-logging them
HOh wait
HDo deployments actually show logs other than errors…
HActually, when are you calling that?
HIn a server route? Globally?
LI define
const apiKeyThat’s probably the issue then. Environment Variables aren’t populated on startup
LHSo you can’t start the API client globally
Loh. so when are they populated?
HOnce the Worker/Function is actually invoked
Lso I can't cache the return value of the OpenAI constructor between invocations?
L(in a global var or otherwise)
HYou could, but you can’t actually construct it until you have received a request
Lok, so what would you recommend for doing that? some kind of nullable memoization type
HJust have a variable that can be an OpenAI API client, but by default is null. Then, whenever you need it, use the variable if present, otherwise initialize it first
