3 ms·
Looking at the response headers from your own site, everything is being served up from Fastly edge servers. Why wouldn't you serve your own site from your own i
by andrewbarba 10y ago
Looking at the response headers from your own site, everything is being served up from Fastly edge servers. Why wouldn't you serve your own site from your own infrastructure?
The reason I even bothered to look at the response headers is because I'm a huge fan of Fastly and wanted to see what you guys were sending back to compare. Turns out they look identical because they are Fastly headers and Fastly edge servers.
And maybe have a look at Fastly pricing: https://www.fastly.com/pricing https://www.fastly.com/pricing $0.0075 / 10,000 requests seems much more reasonable than your $0.05 / 1,000 requests...
- matahwoosh 10y agoWe do serve our own site! We're running multiple apps on the same fly.io domain. Our landing page is currently hosted on Github Pages (and that's probably how you're seeing Fastly headers), but you're hitting our load balancer first :)
- goodroot 10y agoFellow from Fly here, nice to meet you. We do serve our own site. Right now we run multiple applications on our domain. The landing page that you see on http://fly.io http://fly.io is hosted on GitHub pages, which explains Fastly. Our /docs/, too. You are hitting our Load Balancer first, though.