hope it will get fixed once the nameservers update
hope it will get fixed once the nameservers update
CYour DNSSEC Configuration is broken. The reason why it works for some is some ISP DNS Resolvers ignore DNSSEC/do not validate it, but any good public resolver will validate it.
; EDE: 9 (DNSKEY Missing): (no SEP matching the DS found for hysse.dev.)
https://dnsviz.net/d/hysse.dev/dnssec/
It looks like you set up DNSSEC at your Registrar, Porkbun, for a prior DNS Host. You don't appear to have DNSSEC Enabled at Cloudflare.
You’ll want to either outright disable DNSSEC, or enable DNSSEC with Cloudflare and update your DNSSEC configuration with the information Cloudflare gives you:
https://developers.cloudflare.com/dns/additional-options/dnssec/
These changes to your DNSSEC Configuration can be done at your Registrar, Porkbun.
; EDE: 9 (DNSKEY Missing): (no SEP matching the DS found for hysse.dev.)
https://dnsviz.net/d/hysse.dev/dnssec/
It looks like you set up DNSSEC at your Registrar, Porkbun, for a prior DNS Host. You don't appear to have DNSSEC Enabled at Cloudflare.
You’ll want to either outright disable DNSSEC, or enable DNSSEC with Cloudflare and update your DNSSEC configuration with the information Cloudflare gives you:
https://developers.cloudflare.com/dns/additional-options/dnssec/
These changes to your DNSSEC Configuration can be done at your Registrar, Porkbun.
Wchaika op
ZYup. You can use direcct upload for that
Hshould be fixed, thank you so much chaika!
Ghey guys, something im trying to set up which im pretty confident is achievable, but i lack the formal education to implement it myself and wondering if anyone has some wisdom they can share with me
Gim looking to set up 2x documentation websites - one for customers, one for our staff
Gthe staff version, essentially contains all the customer doco, plus some internal reference material
Gideally, this is all on a single URL - someone logs in and based on the domain of their email address, get URL re-written to the correct site
Gi had kinda settled on using docusaurus to build the sites because i think i can pretty easily convince my colleagues to start producing markdown documentation, and ive been able to implement algolia search easily enough as a proof of concept
Gso my challenge is around the inspection of the logged-in user...it would appear that the 'Access' Pages plugin can do the job im after, but actually implementing that in any way whatsoever with docusaurus, is where im struggling to figure things out
Ehttps://github.com/cloudflare/pages-action will give you
idurl, alias and environment as output variables which you can pipe into whatever logic you need in the next action
EThe branch will be automatically inferred from the current git checkout state so if you don't specify anything it will work that out in much the same way that the built-in CI/CD does - but yes if you override the branch then it will largely only impact the branch URL and whether the deployment is production or preview. If you wanted you could write a script to leverage this to customise the preview branch URLs for your deployments
EDirect Uploads is a powerful system, you're running the builds yourself and can send us whatever files you like built however you like with whatever branch name
EAll these branch URLs, they're associated with the same project, yes?Yes, you can setup preview and production builds for each project. Within preview builds there can be many branches, though as far as env vars and bindings for functions goes there can only be the production set and the preview set.
For your use-case I think two projects, one for mainnet and one for testnet, would indeed be a reasonable idea in theory.
Then use push and pull_request triggers in the github actions to deploy to both of these projects from the same trigger (built with the different env vars)Yep this will work fine, just invoke
pages-action twice with different outputs and project namesIf I "invent" a branch name for the pull requests and treat it like a branch name, I can get some friendly deploy preview URLs under the pages.dev domainYep, you can do that. Something like
pr-1234 as branch or similar value.and I would want to handle the closed and merged pull request triggers to remove those same "invented" branches.Yeah you can do that with the API. List them (https://developers.cloudflare.com/api/operations/pages-deployment-get-deployments) and then delete them (https://developers.cloudflare.com/api/operations/pages-deployment-delete-deployment)
Wyeah github uses diff links between users and orgs
Wand we don't know if you are a user or org
Wlong time bug, one day we'll fix it :^)
Tmay I ask if changing this will effect anything? and is it recomended changing this?
TThis is going to sound incredibly stupid, but does cloudflare pages support directory listings?
TWhat can I do for an alternative?
JYou should add this to No Access
CAs Leo mentioned there are programs that will generating the directory list and create html from then
CAny plans to support build caching? Specifically being able to cache npm/pnpm and Next.js (
.next/cache)
CThere is catching planned but no ETA
1DNS over Discord: A records
titanpetsim-codes.pages.dev A @9.9.9.9 +noall +answerdiggy diggy hole
•7/16/23, 10:10 AM
CWhen using next-on-pages, are pages that are statically rendered at build time go through a Worker? Does it use _routes.json to only render the dynamic pages?
JAll routes go through the worker. By default, the only thing that won't invoke the worker is requests to assets in
/_next/static. This is because we follow a routing process through a set of different rules and phases, as defined by Vercel, to ensure that we match incoming requests to the correct destination.