It looks like you have a build process that's adding hashes to your images, but not referencing thos

It looks like you have a build process that's adding hashes to your images, but not referencing those correctly in your built output. This would probably be best in pages-help since I imagine you're going to need to debug what's happening a little further.

JJames It looks like you have a build process that's adding hashes to your images, but ...

Tom4sko•9/25/23, 6:43 PM

done thanks

JamesOP•9/25/23, 6:43 PM

For folks to help you best, I would recommend you provide a copy of your repo, with files so they can reproduce

Unsmart•9/25/23, 10:10 PM

No it only applies to pages actually building it

Lambda•9/26/23, 5:45 AM

Any help is appreciated.

Lambda•9/26/23, 5:45 AM

I'd like my pages.dev to be crawled by search engines like Google

Lambda•9/26/23, 5:45 AM

How can I do that please.

LLambda I'd like my pages.dev to be crawled by search engines like Google

Hello, I’m Allie!•9/26/23, 8:30 AM

Maybe add a robots.txtrobots.txt? Other than that, I don't think I do anything for Flareutils, and it is indexed.

Rich•9/26/23, 12:50 PM

Does anybody have any advice on setting up different environments with Cloudflare Pages. We want a production + preview as well as development + preview environments so that we can point prod to our prod APIs and development to our dev APIs.

Given an app in Cloudflare Pages only offers two envs (production and preview) I was thinking we would need to create a separate app for development vs production.

However, the Cloudflare UI is saying the repo is "In use" with another application, so I can't select it

RRich Does anybody have any advice on setting up different environments with Cloudflar...

Shados•9/26/23, 2:18 PM

I dont know if there's a better way, but we're doing that but publishing directly from a github action instead of using Page's own build.

SShados I dont know if there's a better way, but we're doing that but publishing directl...

Rich•9/26/23, 2:22 PM

That's exactly what I'm researching now

https://github.com/cloudflare/pages-action/

One thing I can't figure out is how to define which branches are preview vs production when using direct upload rather than connecting it to Git -- seems the dashboard loses the ability to configure it.

GitHub

GitHub - cloudflare/pages-action

Contribute to cloudflare/pages-action development by creating an account on GitHub.

bbs_samuray•9/26/23, 4:10 PM

Hello, my next.js project needs to download a zip file from external source and process some data at build time

bbs_samuray•9/26/23, 4:11 PM

Since this processed data won't change, I think doing this with every commit will be wasteful

bbs_samuray•9/26/23, 4:12 PM

Do my build artifacts remain after the build is completed

bbs_samuray•9/26/23, 4:13 PM

Or does it start from scratch every time

Bbbs_samuray Do my build artifacts remain after the build is completed

Hello, I’m Allie!•9/26/23, 4:14 PM

From scratch, unless they are in gitgit, but there is the build-caching-beta, which should hopefully be able to help you there, in the future.

bbs_samuray•9/26/23, 4:22 PM

I am guessing it is in closed beta

bbs_samuray•9/26/23, 4:22 PM

Thanks, I will find a way that is both convenient and not a resource hog

Eeddie soooo how can i www. a cloudflare pages site with a custom domain

Chaika•9/26/23, 8:48 PM

If you already have your apex (example.com) as a custom domain, it's recommended for SEO/etc purposes to just redirect www to apex, ex:
https://developers.cloudflare.com/pages/how-to/www-redirect/
Otherwise, if you're just asking how you can add it, just add it as a custom domain, it's no different then any other subdomain:
https://developers.cloudflare.com/pages/platform/custom-domains/

Samaritan•9/27/23, 2:19 AM

Hi, we have a fairly large Gatsby site that we are porting across from Gatsby Cloud as it shuts down. The site build times are taking between 15-30 minutes to run and I wanted to look at how we can implement caching of the public, node_modules and a .cache folder between build to try and speed up the builds. Is that possible with the Cloudflare pages build system?

SSamaritan Hi, we have a fairly large Gatsby site that we are porting across from Gatsby Cl...

Cyb3r-Jak3•9/27/23, 2:21 AM

There is a beta of build caching, see build-caching-beta. More info at build-caching-beta

CCyb3r-Jak3 There is a beta of build caching, see <#1144554260311326830>. More info at https...

Samaritan•9/27/23, 2:40 AM

Oh awesome, I'll check it out thank you!

addison•9/27/23, 2:43 AM

No Access does anyone know? is there a known issue with the stripe library that causes this? only happens in workers/pages

Rich•9/27/23, 7:53 AM

Does anybody know if it's possible to get the commit hash in a worker or perhaps pass env vars specific to a single deploy?

I'd like to have a /version endpoint in my Remix app which indicates exactly what code is deployed.

RRich Does anybody know if it's possible to get the commit hash in a worker or perhaps...

Hello, I’m Allie!•9/27/23, 8:08 AM

Like this? https://kian.org.uk/cloudflare-workers-build-time-constants-with-wrangler/

Kian's Blog

Cloudflare Workers - Build time constants with Wrangler

Insert Git hashes, Sentry releases or remove debugging code in production environments from your Cloudflare Worker with Wrangler!

HHello, I’m Allie!Like this? https://kian.org.uk/cloudflare-workers-build-time-constants-with-wran...

Rich•9/27/23, 9:12 AM

Yeah I think that might be the solution. TBH I'd rather it be a runtime variable as I've always avoided coupling a build artifact with a deployment... but CF Pages already does a new build per deployment so not really a big deal

kian•9/27/23, 9:13 AM

I don't think Pages can use definedefine

Rich•9/27/23, 9:15 AM

Ah... is that because Pages doesn't have a wrangler.toml file? (At least I don't have one as geneated CF Pages project from Remix CLI)?

Rich•9/27/23, 9:15 AM

Maybe I just need to do a dumb manual token replacement in a postbuild step

RRich Ah... is that because Pages doesn't have a wrangler.toml file? (At least I don't...

Hello, I’m Allie!•9/27/23, 9:19 AM

Now I'm wondering, if Remix uses Vite or something similar, you might be able to do the replacement at the Remix level...

HHello, I’m Allie!Now I'm wondering, if Remix uses Vite or something similar, you might be able to...

Rich•9/27/23, 9:20 AM

Remix uses esbuild but it's not super extensible, but will do some digging

RRich Ah... is that because Pages doesn't have a wrangler.toml file? (At least I don't...

kian•9/27/23, 9:29 AM

Basically

kian•9/27/23, 9:30 AM

Plus, if Remix builds your project, it won't be Wrangler's esbuild that does it

Rich•9/27/23, 9:48 AM

I've asked in the Remix discord here https://discord.com/channels/770287896669978684/770287896669978687/1156524276686528572

But have a feeling they will just say I should define a runtime env var.

It does seem a shame CF Pages doesn't let you define a deployment-level env var.... I guess it's because env vars are request-level in workers so perhaps not coupled to a deployment.

RRich I've asked in the Remix discord here https://discord.com/channels/77028789666997...

Hello, I’m Allie!•9/27/23, 10:12 AM

Env Vars on Pages anyway are coupled to a deployment. For example, if you change vars in the dash, they will only be added on subsequent deploys. This means that you could theoretically get a commit hash or deploy date for each deployment, you would just have to edit the vars on the dash for every deploy

HHello, I’m Allie!Env Vars on Pages anyway **are** coupled to a deployment. For example, if you ch...

Rich•9/27/23, 10:14 AM

I did wonder this, but given they're defined on context.envcontext.env which is bound to a request figured they must change dynamically?

Otherwise I'd love to just have them on global.envglobal.env so I don't have to pass them around to various modules all the time.

Rich•9/27/23, 10:14 AM

If we were to update the env vars via the API in our build script, there'd be a race condition between deploys I expect, it'd need to be passed in as part of the wrangler deploy cmd I expect and not impact other deployments?

kian•9/27/23, 10:16 AM

I did wonder this, but given they're defined on context.env which is bound to a request figured they must change dynamically?

context.envcontext.env is a Pages/Functions wrapper over the fetch(req, env, ctx)fetch(req, env, ctx) that all Workers use. Your resulting built Worker will use export default { async fetch(...) }export default { async fetch(...) }.

kian•9/27/23, 10:17 AM

Otherwise I'd love to just have them on global.env so I don't have to pass them around to various modules all the time.

AsyncLocalStorage is a nicer way to do this, but this is fine. If you use it for arbitrary per-request things (i.e doing globalThis.reqId = "123"globalThis.reqId = "123" then other requests will be able to see and mutate that.

kian•9/27/23, 10:17 AM

If we were to update the env vars via the API in our build script, there'd be a race condition between deploys I expect, it'd need to be passed in as part of the wrangler deploy cmd I expect and not impact other deployments?

wrangler deploy

wrangler deploy

has no way to do this, unfortunately. It is all done in the dashboard/API.

kian•9/27/23, 10:18 AM

It does seem a shame CF Pages doesn't let you define a deployment-level env var.... I guess it's because env vars are request-level in workers so perhaps not coupled to a deployment.

Changing variables doesn't do anything until you do a new deployment, which is a new Worker.

kian•9/27/23, 10:18 AM

A given deployment will always have the same variables.

Kkian > I did wonder this, but given they're defined on context.env which is bound to ...

Rich•9/27/23, 10:30 AM

Interesting, I did briefly look at AsyncLocalStorageAsyncLocalStorage but felt it was a bit complex / overkill, just wanted to shove it on globalThisglobalThis :

export const onRequest = async (
  requestContext: EventContext<any, any, any>
): Promise<Response> => {
   globalThis.env = requestContext.env;
   handleRequest(requestContext.request);
}

export const onRequest = async (
  requestContext: EventContext<any, any, any>
): Promise<Response> => {
   globalThis.env = requestContext.env;
   handleRequest(requestContext.request);
}

However these docs (https://developers.cloudflare.com/workers/runtime-apis/handlers/fetch/#parameters) made me nervous as it says:

env
The bindings assigned to the Worker. As long as the environment has not changed, the same object (equal by identity) is passed to all requests.

But maybe bindings != env vars? (tbh I think I have a bit of a knowledge gap given my first usage of Workers is through Pages)

Fetch Handler · Cloudflare Workers docs

Incoming HTTP requests to a Worker are passed to the fetch() handler as a request object. To respond to the request with a response, return a Response …

kian•9/27/23, 10:30 AM

Bindings are env vars

kian•9/27/23, 10:30 AM

Those docs are for Workers, a given Worker

kian•9/27/23, 10:30 AM

Pages Functions are a different Worker per deployment

kian•9/27/23, 10:30 AM

One cannot affect the other

kian•9/27/23, 10:31 AM

Section 1 on this issue might help you visualise it in the context of Pages

https://github.com/cloudflare/next-on-pages/issues/1#issuecomment-1403845325

It looks like you have a build process that's adding hashes to your images, but not referencing thos

Similar Threads