https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • g
    Shouldn't make any significant difference though, I don't think.
  • i
    The normal A record would be 192.2.0.1, but as you are saying, no difference. Once you have one the other is created automatically if it's proxied. It couldn't be otherwise as Workers wouldn't fire.
  • m
    Ok thanks! Just wanted to make sure as it didn’t seem completely logical to me.
  • i
    They have been saying there needs to be a better way, but it basically needs a record to resolve in DNS as a Cloudflare IP. There should be a button to create a record without origin, saying only: "resolve to Cloudflare, thanks".
  • g
    Definitely would be easier and cleaner!
  • m
    Agreed!
  • i
    Yeah, especially with something like Pages. I guess it's in their backlog, it doesn't even seem that hard to me, it would be mostly cosmetic, behind the scenes could still be a 192.2.0.1 or 100:: record.
  • g
    cc @neynah
  • f
    I have only 
    AAAA 100::
    record, which works just fine
  • k
    hey everyone 👋
  • e
    👋 what are you up to today?
  • k
    meetings 💀
  • k
    i'm hoping to find some time to write a little blog post about my ghost blog -> workers -> discord notifications thing
  • j
    Also, checkout Flareact. It's basically Next.js for Cloudflare workers. https://flareact.com
  • i
    Hey, is it possible to export (i.e. backup) a local copy of a cloudflare namespace? Like a json/file dump or something along those lines
  • i
    The namespace in question isn't altogether that large - a couple hundred kb at most. (ping me if you reply.)
  • g
    Not officially (that I know of). But there is this old script which should be pretty simple to tweak: https://github.com/cloudflare/kv-worker-migrate
  • i
    Thanks, I'll give it a look. fwiw, namespace backups / restoring from backups would be a nice feature.
  • i
    @User looking through the code and documentation, it seems like this utility migrates the contents of one namespace to another and does not download a local copy of the namespace. Do I understand this correctly?
  • g
    Yes. You'd need to tweak it a bit to just dump the namespace contents to a file or something, instead of uploading to the other namespace.
  • i
    I see. any pointers towards which parts of the codebase are responsible for the reupload?
  • g
    Huh, it actually doesn't function the way I thought it did. I thought everything was happening locally, but it actually uses a Worker. Sorry, I was misremembering that. But it still could be useful. Actually, I think you're probably best just starting from scratch.
  • g
    There's two steps to the download: 1) List all the keys (https://api.cloudflare.com/#workers-kv-namespace-list-a-namespace-s-keys) Should be pretty straight forward—just paginate through and ensure to keep the metadata if you want to preserve that. 2) Get each key value (https://api.cloudflare.com/#workers-kv-namespace-read-key-value-pair) Even easier, but will take a while.
  • g
    And then hopefully just one step for an upload: 1) Bulk upload in 10,000 KVs per request (or 100MB, whichever is smaller) (https://api.cloudflare.com/#workers-kv-namespace-write-multiple-key-value-pairs) Should let you set the value and metadata simulatenously.
  • i
    kk, makes sense - thanks for the help! I'm familiar with KV, so I'll probably just roll a quick rust script that grabs each key/value and dumps it all out. It should fall within memory/time limits.
  • d
    can i report someone
  • d
    in this server
  • a
    please DM me
  • s
    Question. Yesterday i started to use Wrangler, because i had some problems with the worker and my s3 bucket. Something doesnt worked yesterday and i made a break. Today i just try it again and now everything works and i didnt changed anything. Is it possible that it takes some time for a few things before they take effect? Its really weird. Its like cloudflare or something else changed something. Im confused.
  • k
    it is very possible - when you deploy a worker it's going to get propagated to all of our edge servers, every once in a while it can take 60s for a build to make it to your local point of presence (cloudflare server nearest to you)
1...454647...2509Latest