Wondering if for small/bootstrapped projects there's any alternative people suggest? Fly has a nice UX and accessible prices, but it's unstable at best. I use the big clouds at work, but for personal they are $$$. Also I want to keep devops tending asymptotically to zero.
Maybe just pick up 3 chonky EC2 boxes, set up iptables on each of them, have each one run a containerized version of your code that gets built and deployed from CI every time you push to Github, slap an ALB in front of it all, and call it a day? And if you need state, then spin up a little RDS with your favorite SQL flavor of choice? The CI deploy script could even bake in little health-checks so you can do rolling d…
Fly.io Postgres cluster down for 3 days, no word from them about it
41–50 of 493 posts
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#42Wondering if for small/bootstrapped projects there's any alternative people suggest? Fly has a nice UX and accessible prices, but it's unstable at best. I use the big clouds at work, but for personal they are $$$. Also I want to keep devops tending asymptotically to zero.
Honestly these days I am leaning towards this approach: https://github.com/mrsked/mrsk/ It's all just docker.
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#43Wondering if for small/bootstrapped projects there's any alternative people suggest? Fly has a nice UX and accessible prices, but it's unstable at best. I use the big clouds at work, but for personal they are $$$. Also I want to keep devops tending asymptotically to zero.
I’m quite happy with https://render.com after leaving Heroku
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#44There is now a response to the support thread from Fly[1]: > Hi Folks, > Just wanted to provide some more details on what happened here, both with the thread and the host issue. > The radio silence in this thread wasn’t intentional, and I’m sorry if it seemed that way. While we check the forum regularly, sometimes topics get missed. Unfortunately this thread one slipped by us until today, when someone saw it and flag…
For what it’s worth, I left Fly because of this crap. At first my Fly machine web app had intermittent connection issues to a new production PG machine. Then my PG machine died. Hard. I lost all data. A restart didn’t work - it could not recover. I restored an older backup over at RDS and couldn’t be happier I left.
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#45Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#46There is now a response to the support thread from Fly[1]: > Hi Folks, > Just wanted to provide some more details on what happened here, both with the thread and the host issue. > The radio silence in this thread wasn’t intentional, and I’m sorry if it seemed that way. While we check the forum regularly, sometimes topics get missed. Unfortunately this thread one slipped by us until today, when someone saw it and flag…
For what it’s worth, I left Fly because of this crap. At first my Fly machine web app had intermittent connection issues to a new production PG machine. Then my PG machine died. Hard. I lost all data. A restart didn’t work - it could not recover. I restored an older backup over at RDS and couldn’t be happier I left.
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#47I really want to love Fly.io. It's super easy to get setup and use, but to be honest I don't think anyone should be building mission critical applications on their service. I ended up migrating everything over to AWS (which I reallllly didn't want to do) because: * Frequent machines not working, random outages, builds not working * Support wasn't responsive, didn't read my questions (kept asking same questions over a…
The answer to _any_ usage related forum question should be:
1. It's in the documentation (maybe I just added it)
2. If you're left with any confusion, let me know and I'll update the documentation to resolve it
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#48Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#49Earlier quoted context omitted.
I wish digitalocean offered decent pricing for spaces (s3). Unfortunately it starts at 5$, which is an enormous price for storing 70 small images, but s3 would greatly simplify my server management moving state entirely outside the server (managed database + managed object storage)
> price for storing 70 small images Do you have to use an object store in that case? Or does it have to be separate from whatever application instance?
The peace of mind of managed is nice, all I have to think about is running the app, without having to deal with making sure db and files don't get lost
Re: Fly.io Postgres cluster down for 3 days, no word from them about it
#50Earlier quoted context omitted.
I wish digitalocean offered decent pricing for spaces (s3). Unfortunately it starts at 5$, which is an enormous price for storing 70 small images, but s3 would greatly simplify my server management moving state entirely outside the server (managed database + managed object storage)
You could use Cloudflare R2, it's pretty cheap overall.