Your credit card number is the thin plastic line between us and chaos. We also have a capitalism nerve that hurts when people spend our money gambling. > We could tell you we want to prevent crypto mining because we care about the planet, and that would be true. > But here's what happens if you give people freemium full access to a hosting platform: lots and lots of free VMs mining for cryptocurrencies. We know that's the worst and it gives you heartburn.
> Even for our free services, we require a credit card number.
#PAMFAX ADDRESS VALIDATION FAILS INSTALL#
What the heck am I missing? Can I just not read? Do I just need to install the CLI and all shall be made clear? I really want to like this service, as we have (at $CURJOB) an app packaged as a docker image that it'd be awesome to set up to run on Fly.io, especially with the multi-region postgresql. * scanned the menu of their docs, and didn't see anything.
#PAMFAX ADDRESS VALIDATION FAILS HOW TO#
* their quickstart docs, which outline how to deploy all manner of applications, except for, you guessed it, an existing docker image. * their getting started guide, called a 'speed run' which has all kinds of CLI commands but doesn't actually show how I'd pick a docker image. * googled 'docker fly' and a blog post that references docker but as far as I can see doesn't have instructions on deploying docker images shows up. I am not sure if I'm missing something or what, but here's where I looked: But because the option exists, we can make this tradeoff on a case-by-case basis, which is so much better than if all we had was "serverless" stuff at the edge and had to choose between just low latency across the globe vs good unit economics.įor a company that says it makes it super easy to deploy a container image and mentions that all you need to do "Write your code, package it into a Docker image, deploy it to Fly's platform", they sure have a dearth of documentation on how to deploy an existing docker container. This provides much better unit economics for many kinds of applications, at the cost of having to manage the scaling ourselves. profitable) business without also charging our customers on a usage basis, or enforcing limits on usage, neither of which is ideal for maximizing engagement as incentives are no longer aligned.įly just gives us compute at the edge for a predictable price per unit of actual compute resources as opposed to requests, and gives us freedom to serve as much traffic as we can min-max onto those resources, like we could with traditional cloud compute.
That's fine for a lot of use cases, but the unit economics of the per request pricing model means it's really hard to operate a predictably sustainable (i.e. Every other edge focused thing out there I'm aware of are "serverless" which these days basically means they charge per request.
0 kommentar(er)
