denoland / denoland/deploy_feedback
Pricing for static file serving
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
If I deploy a compiled Angular or CRA app to Deno Deploy I'll get fast and easy global deployments (which I love) but I'll also pay a fair amount more on egress compared with solutions like AWS CloudFront + S3. Is there a way for Deno Deploy to charge less on egress for static file serving?
Ideally I'd be able to handle requests under /API and be charged the normal amount but then everything else under / that I stream from static files would then be charged a lower fee... or maybe I need to host the static files differently and redirect the client to a CDN...
I guess what I'm wondering is if Deno Deploy can manage that CDN setup and make such redirections easy via code so that I can use Deno Deploy for most, if not all, of my deployment needs while not being concerned about moving or using multiple providers to reduce costs.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.