I’m curious if the pages team is ever going to consider storing logs, the real time logs work perfec

Ssimpson I’m curious if the pages team is ever going to consider storing logs, the real t...

C

Cyb3r-Jak3•9/2/23, 1:38 AM

The only solution right now is using log push which is ent only

RRaindrops is it being considered creating pages without the .pages.dev domain? It would be...

C

Cyb3r-Jak3•9/2/23, 3:09 AM

I doubt it given that custom domains are just CNAMEs of the

.pages.dev

.pages.dev

.pages.dev

.pages.dev domain. You can use bulk redirects to make sure people don't access the main

.pages.dev

.pages.dev

.pages.dev

.pages.dev domain

C

Cyb3r-Jak3•9/2/23, 3:36 AM

Yeah workers you can run on parts of URLs where as pages is the origin server.

H

Hebilicious•9/2/23, 11:24 AM

Hello there, does anyone knows if it possible to have a deploy preview when someone makes a PR from a fork to a github repo configured with the cloudflare integration ?

H

Hebilicious•9/2/23, 11:24 AM

I can see this has been asked many times before, would like to know if there's something in the works

S

simpsonOP•9/2/23, 3:29 PM

Is it possible to clear an entire Pages project cache?

S

simpsonOP•9/2/23, 3:29 PM

It feels like we are seeing issues in our app from caching between deployments

S

simpsonOP•9/2/23, 4:22 PM

On that same note, do any of these settings like purging, browser cache, query string, etc… apply if you are using pages?

S

simpsonOP•9/2/23, 4:57 PM

Do you mean the orange cloud in DNS settings for the custom cname record linked to Pages project?

S

simpsonOP•9/2/23, 5:05 PM

Then you lose firewall rules right?

S

simpsonOP•9/2/23, 5:07 PM

Do you just set the cache level to bypass in page rules

S

simpsonOP•9/2/23, 5:12 PM

Or make a rule in cache rules?

S

simpsonOP•9/2/23, 5:18 PM

I’m looking in the pages docs but I don’t see anything, it would be cool to have a best practices section for how Cloudflare zone services overlap with pages

C

Cyb3r-Jak3•9/2/23, 5:20 PM

Search for cache rules. And you can make a feature request on the docs page

S

simpsonOP•9/2/23, 5:33 PM

I’m curious if there is a difference between page rules and cache rules, it looks like both can be set to bypass

E

Erisa•9/2/23, 5:55 PM

answered in general-helpPage Rules vs Cache rules

A

AlexanderX•9/2/23, 8:23 PM

is it possible to disable pages building if I dont need any building so it will still work with latest files?

A

AlexanderX•9/2/23, 8:26 PM

I can't find "Upload assets"

A

AlexanderX•9/2/23, 8:27 PM

I see it is a thing when creating, but not when connecting to git

E

Erisa•9/2/23, 8:30 PM

Do you not want to use the GitHub integration anymore for the project? Or are the static files stored on GitHub and you just want to remove the build step?

A

AlexanderX•9/2/23, 8:30 PM

the latter

E

Erisa•9/2/23, 8:37 PM

In the project settings, just set the build command to nothing

A

AlexanderX•9/2/23, 8:39 PM

It is already like that, but when I do changes it shows the building process thing and takes a little time to deploy

A

AlexanderX•9/2/23, 8:40 PM

maybe that is unavoidable

A

AlexanderX•9/2/23, 8:43 PM

mhm I checked build logs, it doesn't make any extra delay for build. "No build command specified. Skipping build step"

E

Erisa•9/2/23, 8:44 PM

There should be no timing info next to the build step, and this can show you which step is taking the time

A

AlexanderX•9/2/23, 8:46 PM

yup, thank you

R

rubberburger•9/3/23, 9:44 AM

any idea why i'm getting a 403 from github actions?
afaik, i configured the CF token properly on github (under settings > Secrets and variables > Actions )

As for the CF token, i set its permissions to Account: CF pages: edit (as based on the instructions)

jobs:
    push_migration_to_db_staging:
        ........... <push migrations to supabase>

    deploy_to_cf_staging:
        needs: [push_migration_to_db_staging]
        env:
            <a bunch of environment variables>

        steps:
            ..... some steps

            - name: build next for CF
              run: npx @cloudflare/next-on-pages@1

            - name: Deploy to CF pages
              uses: cloudflare/pages-action@v1.5.0
              with:
                  apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
                  accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
                  projectName: <proj name>
                  directory: .vercel/output/static
                  gitHubToken: ${{ secrets.GITHUB_TOKEN }}
                  branch: dev

jobs:
    push_migration_to_db_staging:
        ........... <push migrations to supabase>

    deploy_to_cf_staging:
        needs: [push_migration_to_db_staging]
        env:
            <a bunch of environment variables>

        steps:
            ..... some steps

            - name: build next for CF
              run: npx @cloudflare/next-on-pages@1

            - name: Deploy to CF pages
              uses: cloudflare/pages-action@v1.5.0
              with:
                  apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
                  accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
                  projectName: <proj name>
                  directory: .vercel/output/static
                  gitHubToken: ${{ secrets.GITHUB_TOKEN }}
                  branch: dev

jobs:
    push_migration_to_db_staging:
        ........... <push migrations to supabase>

    deploy_to_cf_staging:
        needs: [push_migration_to_db_staging]
        env:
            <a bunch of environment variables>

        steps:
            ..... some steps

            - name: build next for CF
              run: npx @cloudflare/next-on-pages@1

            - name: Deploy to CF pages
              uses: cloudflare/pages-action@v1.5.0
              with:
                  apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
                  accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
                  projectName: <proj name>
                  directory: .vercel/output/static
                  gitHubToken: ${{ secrets.GITHUB_TOKEN }}
                  branch: dev

jobs:
    push_migration_to_db_staging:
        ........... <push migrations to supabase>

    deploy_to_cf_staging:
        needs: [push_migration_to_db_staging]
        env:
            <a bunch of environment variables>

        steps:
            ..... some steps

            - name: build next for CF
              run: npx @cloudflare/next-on-pages@1

            - name: Deploy to CF pages
              uses: cloudflare/pages-action@v1.5.0
              with:
                  apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
                  accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
                  projectName: <proj name>
                  directory: .vercel/output/static
                  gitHubToken: ${{ secrets.GITHUB_TOKEN }}
                  branch: dev

R

rubberburger•9/3/23, 9:44 AM

-----------------------

it fails @ the last step (Deploy to CF pages) with this error message

RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:5857:25
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createGitHubDeployment (/home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22110:24)
    at async /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22173:26 {
  status: 403,
  response: {
    url: 'https://api.github.com/repos/<my gh account>/<my repo>/deployments',
    status: 403,
.................

RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:5857:25
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createGitHubDeployment (/home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22110:24)
    at async /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22173:26 {
  status: 403,
  response: {
    url: 'https://api.github.com/repos/<my gh account>/<my repo>/deployments',
    status: 403,
.................

RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:5857:25
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createGitHubDeployment (/home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22110:24)
    at async /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22173:26 {
  status: 403,
  response: {
    url: 'https://api.github.com/repos/<my gh account>/<my repo>/deployments',
    status: 403,
.................

RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:5857:25
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createGitHubDeployment (/home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22110:24)
    at async /home/runner/work/_actions/cloudflare/pages-action/v1.5.0/index.js:22173:26 {
  status: 403,
  response: {
    url: 'https://api.github.com/repos/<my gh account>/<my repo>/deployments',
    status: 403,
.................

S

simpsonOP•9/3/23, 2:36 PM

How are you referencing the secret in your app?

G

guy•9/3/23, 2:38 PM

I've just started paying for the pro workers functions and am using the unbound model, though I'm still getting

Exceeded CPU Limits

Exceeded CPU Limits

Exceeded CPU Limits

Exceeded CPU Limits errors (requests range from 50ms to 2000ms), I thought I would just get billed extra for the additional time, but it's breaking my app

Gguy I've just started paying for the pro workers functions and am using the unbound ...

H

Hello, I’m Allie!•9/3/23, 2:38 PM

Did you redeploy after changing models? IIRC updates to a project are only applied on new deploys

HHello, I’m Allie!Did you redeploy after changing models? IIRC updates to a project are only appli...

G

guy•9/3/23, 2:43 PM

Redeployed and cleared cache, still seem to be getting the error

HHello, I’m Allie!Did you redeploy after changing models? IIRC updates to a project are only appli...

G

guy•9/3/23, 2:53 PM

Even on the deploy specific pages.dev domain, client gets a 503 (Service Unavailable) error and functions logs show another cpu time error

HHello, I’m Allie!Did you redeploy after changing models? IIRC updates to a project are only appli...

G

guy•9/3/23, 2:55 PM

I still see 0 unbound requests though... all of them are going to 'bundled'

G

guy•9/3/23, 3:02 PM

Nevermine I think i was being stupid! I was setting the usage model for pages but needed to set it in the project too!

G

guy•9/3/23, 3:06 PM

Seeing unbound requests going through, but half the time the request just hangs and never resolves lul

Ssimpson How are you referencing the secret in your app?

R

rubberburger•9/3/23, 3:07 PM

i set it under Github settings > Secrets and variables > Actions
afaik the environment variables are fine, someone told me the problem might have to do with me not having set permissions on 'integration as an app' (not sure what this is but i'll have a look)

as a temporary workaround tho, i'm using CF pages deployment webhooks

Gguy Seeing unbound requests going through, but half the time the request just hangs ...

G

guy•9/3/23, 3:55 PM

Quite disappointed with performance here, requests consistently take multiple seconds and sometimes don't resolve at all (at least after 20+ seconds)

K

kian•9/3/23, 3:58 PM

What are you doing in the Worker?

G

guy•9/3/23, 3:59 PM

It's a very basic DB lookup from post request, have tested database speeds and all sub 10ms

Original message was deleted

G

guy•9/3/23, 4:04 PM

That was for the login page, where I'm guessing the hashing stuff took a while... I've tested extensively locally, with wrangler, and on vercel and none of them take over a second ever - I can see in the network tab that the requests are not resolving with cloudflare

Original message was deleted

G

guy•9/3/23, 4:05 PM

Though, this is a seperate issue, unbounded seems to be working now, the requests are just never hitting the CPU i guess? Not a caching thing as I've been trying all day from the same location

Original message was deleted

G

guy•9/3/23, 4:05 PM

bro? I'm expecting my basic requests to resolve in <10 seconds!

Original message was deleted

G

guy•9/3/23, 4:07 PM

I'm using lucia, the hash never takes over 20ms, sometimes even loading the site hangs!

Original message was deleted

G

guy•9/3/23, 4:08 PM

https://github.com/pilcrowOnPaper/lucia/blob/b6ef3eba3f1ad4b3e1b6bcea245d13e663220df0/packages/lucia/src/scrypt/index.ts#L125 based on noble hashes

Original message was deleted

G

guy•9/3/23, 4:13 PM

yup, never even comes close.

Original message was deleted

G

guy•9/3/23, 4:15 PM

I guess so, I still don't feel like any of the operations I'm doing are compute intensive at all though... Doesn't explain the huge variance in response time though

I’m curious if the pages team is ever going to consider storing logs, the real time logs work perfec

Similar Threads