mrkurt

32 ms·

391.
by mrkurt 5y ago
The infrastructure to manage and distribute certificates is pretty complicated, and doing support for certificate issues is expensive. This is why we bill for them. More details here: https://news.ycombinator.com/item?id=226
392.
by mrkurt 5y ago
We're different, but only because we were builtin 2020 instead of 2008. Notably: 1. You get your own Postgres proces and disk, no shared database instances 2. Private networking is baked in. Your app talks to postgres over an encrypted
393.
by mrkurt 5y ago
A user hitting your service would hopefully be hitting your service on Fly.io and that would be talking to a database on Fly.io. :) You can replicate across datacenters on Fly.io for free. No infra engineer required. And very little code ch
394.
by mrkurt 5y ago
This is for people who want to run a fullstack app and expand it to multiple regions. "fly launch" on a Phoenix app, for example, gets your entire app + DB deployed in about 60s for free.
395.
by mrkurt 5y ago
Most people use S3, some people run Minio on Fly. Everyone wants us to just ship object storage so they don't have to think about it.
396.
by mrkurt 5y ago
We do not! You have full administrative access to your postgres. You can create offsite replicas, or even fork the Postgres app we use and deploy over your Fly.io installed postgres: https://github.com/fly-apps/postgres
397.
by mrkurt 5y ago
We run our own servers. It took a lot of work but it's really making life easier now. I'm not sure we could offer a free tier like this on top of another cloud.
398.
by mrkurt 5y ago
It's definitely more hands on. We will be able to do a WAL backup / point in time restore feature when we ship object storage. Managed upgrades are almost in. If you run `fly image show` it'll tell you if you need one, then `
399.
by mrkurt 5y ago
Oh don't you worry. We can extract large sums of money from big companies.
400.
by mrkurt 5y ago
Autoscaling and balancing regions is something we launched with, but it ended up not making much sense. Our load balance sends traffic to the next nearest region when an app is too busy. It's usually better to spread capacity around to
401.
by mrkurt 5y ago
We ended up shipping a "cap your costs" feature, we just did it with prepaid credits. If you buy prepaid credits instead of adding a credit card to your account, we can't bill you more than you've prepaid. The downside i
402.
by mrkurt 5y ago
We have no ARM plans, but a strong desire. The really good ARM stuff is locked up within Apple and Amazon, though. I'm really hoping an independent chip vendor ships a compelling and broadly available ARM platform we can use for server
403.
by mrkurt 5y ago
We started with generic Docker! The Phoenix focus has been very helpful, though. Docker apps are incredibly broad, other than "it's really easy to launch a container", it's hard to define why we're especially good a
404.
by mrkurt 5y ago
The API is open. If you spelunk through flyctl you can see it using GraphQL for everything: https://github.com/flyctl
405.
by mrkurt 5y ago
Every app on Fly runs in a dedicated private network over wireguard. So yes!
406.
by mrkurt 5y ago
You can run multiple DBs in a single postgres instance. "fly pg attach" creates a DB and user for each app you run.
407.
by mrkurt 5y ago
Now I wish it had been. That's hilarious.
408.
by mrkurt 5y ago
Read heavy Rails apps work great multi region: https://fly.io/blog/run-ordinary-rails-apps-globally/ We have a Gem to make it almost transparent: https://github.com/superfly/fly-ruby
409.
by mrkurt 5y ago
This is it.
410.
by mrkurt 5y ago
Ah, for this you want "fly launch", it'll tell you it's going to generate a config file for you. Edit the config so the `internal_port` is right for the app you're running, then `fly deploy -i fusionauth/fusion
411.
by mrkurt 5y ago
You know, you're not really missing anything, we just don't connect the dots very well. Install CLI, run `fly launch` in a directory with a Dockerfile, and it should just work. Most of our users don't start with a Docker imag
412.
by mrkurt 5y ago
Not quite, but pricing is a little complicated AND we haven't shipped multi-shared CPU VMs yet. Postgres prices are a function of the underlying resources. There are a bunch of steps between $7 and $28, you can put any size volume you
413.
by mrkurt 5y ago
It's an attempt to reduce friction. Developers try services like ours out for fun before they use them in anger. Putting a price on the fun stuff keeps people from trying it. It's not that $6.88/mo is too much, it's that
414.
by mrkurt 5y ago
We include 160GB of outbound bandwidth per month: https://fly.io/docs/about/pricing/#free-allowances
415.
by mrkurt 5y ago
Oh goodness I love KubeSail. Before Fly.io, I really wanted to build a self hosted alternative to Google Photos. I think what you're doing is incredibly valuable.
416.
by mrkurt 5y ago
This is true, but we aren't going to bill per request. We really can't, since we support arbitrary UDP and TCP services. I don't really want to promise anything we haven't shipped yet. But my perfect cloud service (a) ch
417.
by mrkurt 5y ago
We're working on this. I don't like the credit card barrier. It adds friction to a thing we want a lot of people to try out.
418.
by mrkurt 5y ago
shhh!
419.
by mrkurt 5y ago
It's worth noting that our 3GB free is a quirk of our infrastructure. We want people to try a read replica. We only provision volumes down to 1GB. 3GB sounds better than 2GB. Sometime soon we'll cross the threshold of relevance an
420.
by mrkurt 5y ago
I'm sad this bug burned you. We had some brittle infrastructure for talking into a Postgres cluster, and it was a bit of a fire drill to rip it out and simplify. You would have a better experience if you tried today! We know this becau

More ›