Define serverless email? You’d need a worker with an email trigger and a different service to send e
Define serverless email? You’d need a worker with an email trigger and a different service to send emails but it should technically be possible
CSomething that behaves like a traditional email server is probably the easiest way of putting it. At minimum be able to store emails from email workers and then serve them to a mail client using IMAP, I'm less sure if the reverse operation is possible of taking a mail client request to send an email and then sending it from that email address.
CYou won’t be able to have an imap client because workers/pages only workers with HTTP
CSadness :( a web gui email system would be jank as all hell but possible I guess then?
CYeah you’d still need a service for sending emails but it should work
CAh that slightly sucks, I'd love to be able to do all my email stuff for services inside cloudflare's service but it looks like an email server is kinda unavoidable. :/
Janyone know how to fix a react app in typescript that won't deploy
JI have the environment vars correct, but I'm getting generic typescript errors, and it won't deploy
HYou could use JMAP tho
HJust got to get Thunderbird onboard
CThat's a shout, thank you for the pointer, unfortunately I'd completely forgotten about the limit that the workers can't send mail to unverified emails so it'd still be hamstrung but it would let me create separate mailboxes for emails on my cf domains.
HYou just need an outbound provider like SendGrid or Mailgun
Fhas anyone here deployed an astrojs application to pages?
there are two ways to define api endpoints. astro has built in way. you just define a js file in your pages directory and it becomes an endpoint on your server.
like so:
cloudflare handles this fine. from my webpage i can execute the function with
but when i try the 'cloudflare way' of defining a function:
i cannot reach it from my webpage with
there are two ways to define api endpoints. astro has built in way. you just define a js file in your pages directory and it becomes an endpoint on your server.
like so:
cloudflare handles this fine. from my webpage i can execute the function with
fetch('/api/endpoint.json')but when i try the 'cloudflare way' of defining a function:
i cannot reach it from my webpage with
fetch('/api/helloworld'). i get a 404. however i can reach it fine when running locally with wrangler
EI have, I do them what you call the "cloudflare way" https://github.com/Erisa/erisa.uk/tree/main/functions
Note that functions needs to be in the root directory of the project, which it is in that case right?
Note that functions needs to be in the root directory of the project, which it is in that case right?
Fyes my cloudflare way looks like this:
i can see in my dashboard that the helloworld function did indeed deploy. it's just that i get a 404 when trying to
i can see in my dashboard that the helloworld function did indeed deploy. it's just that i get a 404 when trying to
fetch it from my webpage: fetch('/api/helloworld')F
F
EI dont think using both simultaneously will work
Fit's weird how you use the regular page function way and it works for you, but i use both and only the astro way works 
as i mentioned, when i run the project locally with wrangler, it all works fine. but once deployed, the cloudflare function style seems unreachable
as i mentioned, when i run the project locally with wrangler, it all works fine. but once deployed, the cloudflare function style seems unreachable
EIf you look at the routing configuration, astro is capturing
/:path and routing all requests through it - this likely is taking priority over your own functionEMine works because I dont have the astro method configured, it is deployed as a static Astro site with a functions dir
Foooh you have it as a static site with a functions dir? awesome i didn't know that was possible. i didn't bother trying. i thought i had to deploy mine with SSR
EIf youre using the astro managed functions then yeah
Ebut if youre just using the cloudflare /functions then no need to be SSR
Fthat's good to know. i was a little sad i thought i had to use SSR. all of the tutorials (cloudflare and astro) mention having to use the astro-cloudflare plugin which seems to turn your project into SSR
EI dont blame them because the SSR features are no doubt very nice to use when you need them
EBut no, Pages will work completely fine with a static Astro site
Fthank you so much for your help
CConsider checking on Dash -> Pages to check for build status everytime I push, is there way to get push notification?
JLong polling for build status is a good solution, it’s what https://github.com/WalshyDev/cf-pages-await does
GitHub
Wait for your Cloudflare Pages builds to finish! Contribute to WalshyDev/cf-pages-await development by creating an account on GitHub.
JYou could also do something a bit lower tech like
curl some endpoint after your build script runs in pages ci. Not perfect, but might be good enough?
CI wish a mobile app + push notifications 
COh sorry, I didn't see it clearly. By using Github Actions, I'll get push notifications on my Github Mobile app? 
JYou could set something like that up I imagine, yes
Cthe repo doesn't say what API_TOKEN permissions are required.
FI did some more careful reading and building sample projects. And either there is a bug or cloudflare needs to update their documentation about deploying an astro site. My observations:
https://developers.cloudflare.com/pages/framework-guides/deploy-an-astro-site/
https://docs.astro.build/en/guides/deploy/cloudflare/
replicate the issue with SSR:
both astro and cloudflare docs need to be updated to make this limitation clear IMO. the cloudfare docs make it seem as though you can use the functions directory while using SSR but this is not the case. (unless i'm doing something wrong)
- if you deploy an astro site using the astro cloudflare plugin (SSR), you cannot use the /functions directory. you must use astro endpoints
- if you deploy astro static site (don't use astro cloudflare plugin), you can use the /functions directory
https://developers.cloudflare.com/pages/framework-guides/deploy-an-astro-site/
https://docs.astro.build/en/guides/deploy/cloudflare/
replicate the issue with SSR:
both astro and cloudflare docs need to be updated to make this limitation clear IMO. the cloudfare docs make it seem as though you can use the functions directory while using SSR but this is not the case. (unless i'm doing something wrong)
Astro is an all-in-one web framework for building fast, content-focused websites. By default, Astro builds websites that have zero JavaScript runtime …
Astro Documentation
How to deploy your Astro site to the web using Cloudflare Pages.
EThe behaviour is intentional so it must be a documentation problem, feel free to submit a docs PR yourself or I can later
Scan anyone help me make a copy
CDoes it build locally? It could be that firebase isn’t compatible with the workers runtime
Swhen connecting custom domains, does it count as two towards total count if you add www.domain.com and domain.com?
Eyes
Sbummer
Sso realistically you get half of the advertised domains
CHow so? They are separate domains
HNote that for SEO reasons, it is actually better to only have one of the domains as your custom domain(
domain.com or www.domain.com), and then have the other redirect to the first. This can be accomplished with a Redirect Rule, so you won't consume a Custom Domain slot.SIs there any benefit of one over the other?
HHere's a guide, but other than some things with cookies, it is up to personal preference. Just pick one, and stick with it.
