Is there a timeline for logpush on pages? I'm considering building a custom solution using the Taill
Is there a timeline for logpush on pages? I'm considering building a custom solution using the Taill WebSocket.
HOther than calling out to the API manually, no
HD1 has had an API since basically when it was created, though we do generally recommend you use a Worker as a proxy because it is kind of slow
Interact with Cloudflare's products and services via the Cloudflare API
HFor one-off stuff you do in a build tho, it should be good enough
&Hi, I am having problems linking the root domain to a correctly deployed page, any ideas?
These are the CNAMEs, I have not configured any other record type
These are the CNAMEs, I have not configured any other record type
HWhich one do you want to be the canonical page?
domain.com? Or www.domain.com?
&domain.comHKeep the first CNAME. Convert the second CNAME into an AAAA record pointing to
100::www.domain.com to domain.com like so:
HCloudflare Docs
To create Bulk Redirects in the Cloudflare dashboard you must:
&Okay, I think I got it, I'll try and try again
&Okay, I don't know how long it takes to update the DNS but I'm getting this response 
&Would it be a good idea to open a forum to help with this topic?
NDo cf pages set some special environment variables?
NLike, for example some kind of request ID that I could attach to my logs to group by request
NTbh not even sure if that'd work
HThat would probably be a ray-id, though those are on the request, not the env
Nah alright, so i cant use it in my global initialization of the logger 
HI mean, if you initialise it in the middleware, you could?
Neee
Nim doing next-on-pages
Nand just export a logger
Ndont think i can do that dynamically without making it annoying to me (like having to call
createLogger(request) to access it)HOk, not entirely sure since it is
next-on-pageswell it is just a function
Ni could maybe initialize the logger with an export let
Nthen reassign in the middleware?
HThat could work?
NI'll try that
None worker shouldnt be reused across requests right?
UA worker can and will be reused
HIt can be, though it is generally tied to a single browser call
UYou should never use global scope for request level data (really in any serverless env)
NHoh wait
HYeah, that
Njust tryna add some per-request id to my logs
Uyou can use something like async local storage that you run per request that contains the request id
Nlogs are sent from the server
Nand are unfortunately not async
Nunless im misunderstanding
UYou can still use ALS
Nas in the import from async_hooks ?
Uhttps://nodejs.org/api/async_context.html
Log with ID is actually the example on the docs for async local storage
Log with ID is actually the example on the docs for async local storage
Nthought that was node
Ucloudflare supports node apis ALS being one of them
Nnice
