- Receive the image from the user or whatever the API route is - Save it and tag it (Give it an ID and save information about it for later on) - Add it to the end of some kind of queue file - Every so often, go to the first image on the queue, take it off the queue, process it and then send it to Cloudflare R2
Guys I am a little bit confused. Just configured Cloudflare for the first time. Already changed my nameservers as well and got the message: Great news! Cloudflare is now protecting your siteGreat news! Cloudflare is now protecting your site.
Now, how can I configure Cloudflare to follow cache rules based on whatever the origin specifies in the CDN-Cache-Control header? For all kind of files, like HTML, JS and JSON.
Do I need to create a "Cache Rule" or a "Page Rule" or even something else?
Cloudflare respects the origin web server’s cache headers in the following order unless an Edge Cache TTL cache rule overrides the headers. Refer to the Edge TTL section for details on default TTL behavior.
I'm not sure if this is a great place to ask, but would it be a good idea to self-host an outbound only email server on one of my servers running in the cloud?
It has a dedicated IP address and I can set it up with DMARC on Cloudflare so that it's not instantly rejected by other email servers.
I want to use this primarily for email verification emails, forgot password links or a "magic" link
You need to find an (IPv4) IP (or two) which are not in the common block lists, which is hard, because some block entire VPS ranges or VPS provider simply block outgoing SMTP (e.g. Hetzner). You can't host a mail server on Cloudflare.