Ah, okay. Excited to see what's to come.

Oh yeah, it absolutely is.

Well thanks for the info. Hopefully the proxy dosn't take long because it would be a great addition to my toolchain.

I don’t know what the team’s plans are for Christmas, but I am pretty confident we will see a new round of fixes drop before before then.

typescript
// Connect to MongoDB realm
async function connect(env: any): Promise<globalThis.Realm.Services.MongoDB | Error> {
    try {
        console.log(env.REALM_APPID);
        App = App || new Realm.App(env.REALM_APPID);
        const credentials = Realm.Credentials.apiKey(env.env.REALM_AUTH_API_KEY);
        const user = await App.logIn(credentials);
        return user.mongoClient('mongodb-atlas');
    } catch (err) {
        console.log(err);
        throw err as Error;
    }
}

Here I'm just binding REALM_APPID from the command line

I just had to switch it from env.REALM_APPID to env.env.REALM_APPID

I'll post more when home

Yeah, Pages Functions only has 1 argument called context, which has an ‘env’ property.

If you see the examples, they deconstruct with {} around the env.

If I destructure it, it works on wrangler, but on staging:

TypeError: Cannot read properties of undefined (reading 'REALM_APPID').

it was working fine until last night 😭

there isn't a log tab for pages, eh?

looks like

env

, destructured or not destructured, is undefined on staging 💀

You need to define your settings for every environment in the Pages Dashboard..

should be good

also, I mean env is completely undefined, no "ASSETS" or anything

let me double check that actually, I might've messed up

yea I json stringify env, returns undefined

just to clarify, both

env

and

{ env }

Can you DM me the whole thing? Including the

onRequest*()

call?

1m

Using wrangler locally would it pick up env vars defined in

wrangler.toml

? I'm able to see the ASSETS property but nothing else

No, you have to manually specify those with wrangler.. -kv or something to the

pages dev

command

Thanks good to know. Is there any way to see logs from deployed function executions at the moment or not yet?

Not yet unfortunately

are there any way to cache 'cloudflare pages function' response to save resources?

You can achieve that by using a custom domain and, optionally, creating a Page Rule with

Cache Everything

.

Worker run before the cache, so I am pretty sure that won't actually prevent the worker from being run..

Regular Workers do, yeah, but Pages aren't served from your zone - afaik it is more like a SSL for SaaS setup. Whether this feature is intentional or not, I'm managing to cache responses from Functions: https://pagestest.asp.gg/time

Ahhh.. yeah indeed. You are correct. It is indeed SSL for SaaS under the hood..