You can’t. All bindings are configured via the dash

HHello, I’m Allie!You can’t. All bindings are configured via the dash

A

Avi•10/2/23, 6:54 AM

ah yeah, i saw that you need to do it via the dash or API. seems like a pretty massive missing feature

A

Avi•10/2/23, 6:55 AM

particularly for CI usage

I

iBug•10/2/23, 8:03 AM

Any plans to add MkDocs for build cache? I'm hosting a few documentations on Pages and I'd like to see MkDocs cached

G

Gido.K•10/2/23, 8:54 AM

I am getting this error "You have no linked accounts matching the provided username. (8000011)" when trying to deploy a Github repo to Cloudflare pages with terraform. How can i fix this?

HHello, I’m Allie!Maybe add a `robots.txt`? Other than that, I don't think I do anything for [Flar...

L

Lambda•10/2/23, 9:31 AM

Very strange. Maybe something went wrong on my page, maybe they are considered bad?

R

Relequestual•10/2/23, 10:59 AM

Is it possible to "disable" or "turn off" a pages site?
I want to remove some, but I want to double check there won't be any impact before deleting them.
They should be deprecated and no longer needed, but I'd like the "undo" to be fairly easy

Z

zegevlier•10/2/23, 11:00 AM

You could make a new deployment to them with only an error page. Then you can rollback the deployment if you notice any problems.

K

Kuririn•10/2/23, 11:17 AM

I had an error during build: error: failed to download node-v16.14.2-linux-x64.tar.gz and deployment is stuck, it should restart or something

K

Kuririn•10/2/23, 11:17 AM

I also have caching on, why node version is not cached?

I

Isaac McFadyen•10/2/23, 11:22 AM

Have you deployed before? Build caching caches your previous deploy's artifacts, so if you haven't successfully built the cache will be empty.

I

Isaac McFadyen•10/2/23, 11:22 AM

As for that Node version, what is your

.node-version

.node-version

or

NODE_VERSION

NODE_VERSION

environment variable set to?

K

Kuririn•10/2/23, 11:28 AM

yes, I've deployed successfully before, I see it try again after 10 minutes (still didn't work, but going direct, link works), but if it was cached it there would be no problem
I have NODE_VERSION set to 16.14.2

K

Kuririn•10/2/23, 11:31 AM

12:11:22.242 Success: Finished cloning repository files
12:11:22.916    Restoring from dependencies cache
12:11:22.939    Restoring from build output cache
12:11:23.506    Success: Dependencies restored from build cache.
12:11:23.621    Detected the following tools from environment: nodejs@16.14.2, npm@9.6.7
12:11:23.623    Installing nodejs 16.14.2
12:11:24.844    Trying to update node-build... ok
12:11:25.139    Downloading node-v16.14.2-linux-x64.tar.gz...
12:11:25.139    -> https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.gz

12:11:22.242 Success: Finished cloning repository files
12:11:22.916    Restoring from dependencies cache
12:11:22.939    Restoring from build output cache
12:11:23.506    Success: Dependencies restored from build cache.
12:11:23.621    Detected the following tools from environment: nodejs@16.14.2, npm@9.6.7
12:11:23.623    Installing nodejs 16.14.2
12:11:24.844    Trying to update node-build... ok
12:11:25.139    Downloading node-v16.14.2-linux-x64.tar.gz...
12:11:25.139    -> https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.gz

12:11:22.242 Success: Finished cloning repository files
12:11:22.916    Restoring from dependencies cache
12:11:22.939    Restoring from build output cache
12:11:23.506    Success: Dependencies restored from build cache.
12:11:23.621    Detected the following tools from environment: nodejs@16.14.2, npm@9.6.7
12:11:23.623    Installing nodejs 16.14.2
12:11:24.844    Trying to update node-build... ok
12:11:25.139    Downloading node-v16.14.2-linux-x64.tar.gz...
12:11:25.139    -> https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.gz

12:11:22.242 Success: Finished cloning repository files
12:11:22.916    Restoring from dependencies cache
12:11:22.939    Restoring from build output cache
12:11:23.506    Success: Dependencies restored from build cache.
12:11:23.621    Detected the following tools from environment: nodejs@16.14.2, npm@9.6.7
12:11:23.623    Installing nodejs 16.14.2
12:11:24.844    Trying to update node-build... ok
12:11:25.139    Downloading node-v16.14.2-linux-x64.tar.gz...
12:11:25.139    -> https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.gz

K

Kuririn•10/2/23, 12:46 PM

ok, thanks

B

Barry•10/2/23, 2:05 PM

Any idea when hyperdrive bindings will be available for pages?

R

Rich•10/2/23, 4:51 PM

Does anybody know if it's possible to have wrangler (or more specifically the Pages Github action cloudflare/pages-action) ignore certain files inside of the directly of static files?

My specific use case is preventing source maps from being uploaded...

R

Rich•10/2/23, 5:20 PM

Ok seems reasonable. Thanks for the tip! I went with

find

find

as I think

rm **/*.js.map

rm **/*.js.map

would also remove directories with that name (could be wrong though

)

find public -type f -name \"*.js.map\" -delete

find public -type f -name \"*.js.map\" -delete

R

Rich•10/2/23, 5:42 PM

Somewhat relatedly, does anybody know how to handle sourcemaps with Pages Functions?

I'm using Remix which is generating the following bundle along with the sourcemap

functions/
├── [[path]].js
├── [[path]].js.map

functions/
├── [[path]].js
├── [[path]].js.map

Which I'm then uploading to my error monitoring platform (sentry), however the raw stack traces in sentry suggest my function is going through a second round of bundling by CF Pages, so the sourcemaps aren't found?

Error: [preview] Error on *server render*
  at IS(functionsWorker-R.EDACTED.js:11131:12)
  at AE(functionsWorker-R.EDACTED.js:3788:30)
  at Cp(functionsWorker-R.EDACTED.js:2825:41)

Error: [preview] Error on *server render*
  at IS(functionsWorker-R.EDACTED.js:11131:12)
  at AE(functionsWorker-R.EDACTED.js:3788:30)
  at Cp(functionsWorker-R.EDACTED.js:2825:41)

Error: [preview] Error on *server render*
  at IS(functionsWorker-R.EDACTED.js:11131:12)
  at AE(functionsWorker-R.EDACTED.js:3788:30)
  at Cp(functionsWorker-R.EDACTED.js:2825:41)

Error: [preview] Error on *server render*
  at IS(functionsWorker-R.EDACTED.js:11131:12)
  at AE(functionsWorker-R.EDACTED.js:3788:30)
  at Cp(functionsWorker-R.EDACTED.js:2825:41)

R

Rich•10/2/23, 6:45 PM

It sounds although we might need to use Advanced Mode https://developers.cloudflare.com/pages/platform/functions/advanced-mode/

As it sounds although a

_worker.js

_worker.js

file doesn't get modified like the functions directory does so we can have it built by Remix w/ sourcemaps.

Basically would have to move this into our own code

https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/templates/pages-template-worker.ts

R

Rich•10/2/23, 7:01 PM

It's interesting reading the code in

pages-template-worker.ts

pages-template-worker.ts

... I had assumed that multiple "Functions" in

functions/*.js

functions/*.js

would be deployed as separate workers (and Remix was just making that redundant with a catch all route

functions/[[path]].js

functions/[[path]].js

), but it seems like the functions dir is like it's own little framework which get's bundled into a single worker?

So if you're using Remix, you might as well just use

_worker.js

_worker.js

directly

Rryan-exp Hi, posting this question as we had a production issue, and am wondering if anyb...

E

Erisa•10/2/23, 8:11 PM

Cloudflare Pages Availability Issues

E

Erisa•10/2/23, 8:11 PM

For any preview deployments made between 17:19 UTC and 19:24 UTC, Cloudflare Pages is serving those deployments on the production URLs (project_name.pages.dev and any custom domains).

Rryan-exp Hi, posting this question as we had a production issue, and am wondering if anyb...

B

benthecarman•10/2/23, 8:42 PM

yeah this just happened to us

EErisa probably related to https://www.cloudflarestatus.com/incidents/t53r6tfsg1sj ?

B

benthecarman•10/2/23, 8:43 PM

wow this is really bad.. lost our users some money..

F

futurepaul•10/2/23, 8:48 PM

yeah, will there be a post-mortem for this one? need to know what measures will be taken for this to not happen again. would suck to live in fear of dev versions being deployed

T

tony19•10/2/23, 8:59 PM

Hi, can pages respond with partial content?

Ffuturepaul yeah, will there be a post-mortem for this one? need to know what measures will ...

U

Unsmart•10/3/23, 2:08 AM

If you have an enterprise account you can request an incident report but generally if you dont have an enterprise account it comes down to if they write a blog about it

CChris This is a disastrous issue. What can we do to avoid the risk of this in the futu...

C

Cyb3r-Jak3•10/3/23, 2:17 AM

Realistically there isn't anything that can be done on your side. It is all on Cloudflare

A

Avi•10/3/23, 4:56 AM

is anyone aware of limitations with the Pages local dev server that would cause it to throw 500 errors if it's under too much load?

A

Avi•10/3/23, 4:56 AM

because that's what i seem to be getting when i run my (highly parallelized) test suite against it

A

Avi•10/3/23, 4:57 AM

they are intermittent and for static assets (proxied via

vite dev

vite dev

vite dev

vite dev), no apparent rhyme or reason

A

Avi•10/3/23, 5:04 AM

[WebServer] [pages] [mf:inf] GET /src/components/Scope.tsx 500 Internal Server Error (273ms)
[WebServer] [pages] [mf:err] Error: Network connection lost.

[WebServer] [pages] [mf:inf] GET /src/components/Scope.tsx 500 Internal Server Error (273ms)
[WebServer] [pages] [mf:err] Error: Network connection lost.

[WebServer] [pages] [mf:inf] GET /src/components/Scope.tsx 500 Internal Server Error (273ms)
[WebServer] [pages] [mf:err] Error: Network connection lost.

[WebServer] [pages] [mf:inf] GET /src/components/Scope.tsx 500 Internal Server Error (273ms)
[WebServer] [pages] [mf:err] Error: Network connection lost.

A

Avi•10/3/23, 5:04 AM

seems to be that these "Error: Network connection lost." messages are associated with it

A

Avi•10/3/23, 5:05 AM

there are exactly six 500 errors, and exactly six of those exact "Network connection lost" messages

A

Avi•10/3/23, 5:49 AM

yeah, it seems like sometimes the pages dev server just... decides... not to forward requests on to the proxy command and just 500s instead

A

Avi•10/3/23, 7:01 AM

update: this is happening even with pages serving a static asset directory. so it's not related to the proxying command feature

R

Rich•10/3/23, 9:36 AM

Does anybody know where your

_worker.js

_worker.js

file needs to live in order to use Advanced Mode?

https://developers.cloudflare.com/pages/platform/functions/advanced-mode/

that says "Pages offers the ability to define a _worker.js file in the output directory of your Pages project.", however I'm not sure where the output dir is exactly, I tried defining in the cwd but it doesn't seem to have worked...

R

Rich•10/3/23, 9:45 AM

Ok I just figured it out, it has to live in the same directory as your public static assets...which is kinda scary in case there was a bug which uploaded it as a static asset

C

Cyb3r-Jak3•10/3/23, 12:10 PM

What do you mean renders twice?

K

kian•10/3/23, 12:25 PM

Try disabling Auto Minify for HTML on your custom domain's zone.

You can’t. All bindings are configured via the dash

Similar Threads

Similar Threads

Similar Threads