Earlier quoted context omitted.
No. Flyctl SSH does not allow this functionality.
We definitely don't do SFTP! My general M.O. for moving files to running VMs is Magic Wormhole. But that's not optimal either. You've got a legit irritation and I'm glad you put it on our radar.
Fly.io: The reclaimer of Heroku's magic
171–180 of 320 posts
Re: Fly.io: The reclaimer of Heroku's magic
#172Earlier quoted context omitted.
> Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business. Guess what? fly.io offers a turnkey distributed/replicated Postgres for just this reason. You use an HTTP header to route writes to the region hosting your primary. https://fly.io/docs/getting-started/m…
> Guess what? fly.io offers a turnkey distributed/replicated Postgres for just this reason. You use an HTTP header to route writes to the region hosting your primary. Doesn't this take away a lot of the benefits of global distribution? For example if you pay Fly hundreds of dollars a month to distribute your small app in a few datacenters around the globe but your primary DB is in California then everyone from the EU…
Re: Fly.io: The reclaimer of Heroku's magic
#173Can someone explain what fly.io actually is for someone with an AWS background?
It's a platform as a service. It'll take your docker application (usually a web application) and run it on the internet. It'll also allow you to run it in many locations around the world transparently (using the same IP address / anycast) so that users closer to those locations will get better/lower latency.
It's a CDN for your application.
(There's more to it than this, but as far as elevator pitches go, sufficient?)
Re: Fly.io: The reclaimer of Heroku's magic
#174After all the chatter this week, I've come to the conclusion that Heroku froze at the perfect time for my 4 person company. All of these so called "features" are exactly what we don't want or need. 1. Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business. 2.…
I have used multi-region for every production database I've deployed in the last ~8 years, and it took There is a benefit if you're multi-region (but not global) because individual regions go down all the time.
It costs more every month, but if you have a B2B business, it's worth the extra cost.
Re: Fly.io: The reclaimer of Heroku's magic
#175After all the chatter this week, I've come to the conclusion that Heroku froze at the perfect time for my 4 person company. All of these so called "features" are exactly what we don't want or need. 1. Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business. 2.…
Even small companies should be multi-region, if they care about uptime.
Re: Fly.io: The reclaimer of Heroku's magic
#176Earlier quoted context omitted.
How about large traffic from a legitimate spike (e.g. front page of reddit or HN)? You have enumerated a lot of alternatives so far (prepaying, waiving attack costs) but you still haven't addressed the number one scenario that everybody has been asking about, and which was the reason why Heroku was such a hit: do you offer a flat fee which, if exceeded, simply shuts down the app until the next billing cycle?
"We also waive fees from big, legitimate bursts."
Re: Fly.io: The reclaimer of Heroku's magic
#177For a toy app, 10k db rows (across all tables) from Heroku was enough to get the app running and have a public URL to share, and I miss those days.
I'm working on a fresh Rails7 toy app to try out some new features, and my current thinking is to use sqlite, and add an initializer early in the stack to migrate+seed the db if it's missing. If it's ephemeral that's fine, I just want some baseline data to interact with the app at a distance beyond localhost.
Re: Fly.io: The reclaimer of Heroku's magic
#178The one thing I'm really missing after looking at a number of hosts (Fly and Render being top of list otherwise) is a free database tier. For a toy app, 10k db rows (across all tables) from Heroku was enough to get the app running and have a public URL to share, and I miss those days. I'm working on a fresh Rails7 toy app to try out some new features, and my current thinking is to use sqlite, and add an initializer e…
Re: Fly.io: The reclaimer of Heroku's magic
#179Earlier quoted context omitted.
Neat, I'd say that is absolutely HN frontpage worthy!
And disclosure, I used to be on Azure Front Door team and was the lead for Azure Edge Zones development. I really wanted to do something like fly with that. But it turned out that too many people wanted too many different things. Some needed GPU (some Nvidia, some AMD), some FPGA, some general compute. Surprisingly few cared about Functions (our Lambda-like service), or even Web Apps (our Heroku). SQL Server was a bi…
Re: Fly.io: The reclaimer of Heroku's magic
#180Earlier quoted context omitted.
Can you not ssh into a fly instance and then pull?
No. Flyctl SSH does not allow this functionality.