Just for the Fly.io team's notice, the monospaced text (the "cli commands") renders badly when one is using the Dark Reader browser extension.
Free Postgres databases for small projects
211–220 of 231 posts
Re: Free Postgres databases for small projects
#212Earlier quoted context omitted.
Arbitrary UDP has worked since we launched UDP; it's never had a port filter or anything.
My bad, it was v6 UDP I was thinking of? I'm a big fan of Fly and have one medium-sized app deployed to it. Just waiting on this specific issue before deploying more: https://community.fly.io/t/allow-non-root-users-to-write-to-...
You're not crazy! We still don't do v6 UDP (there's no good reason for us not to, but it'll be a week of rebuilding a BPF engine while the plane's still in the air, so this task never hits the top of our stack and won't until someone really pressures us on it). Full honesty! That's how we roll on HN. :)
Re: Free Postgres databases for small projects
#213Earlier quoted context omitted.
Yes, see what they wrote after fully charging me and refusing a charge back: > There are some security issues with your account. We need to verify the > account holder in order to unlock your account again. > Please send us a scanned photo ID of the account holder and also a Letter of > authority (LOA). It is required that the entered account information are > also shown on the proof. > We will then enable your PamFa…
Merchants can't just refuse a chargeback. The entire point of a chargeback is that it's clawing money back from an unwilling merchant.
Not with a debit card without insurance.
Re: Free Postgres databases for small projects
#214Earlier quoted context omitted.
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 image though, they start with Phoenix. What you're seeing is a little bit of indecisiveness in how we target the docs.
Any chance of getting autobuilder support for Rust? :) What about same for .NET? (and I suppose some people would care about Java,Kotlin,Swift ;) I don’t have to deal with containers with my current infrastructure, and it would be nice if I didn’t just to be able to use Fly—I find containers to be a PITA. Thanks! I’m super jazzed about Fly :D
Yes there's a good chance for all of these! You can post on community.fly.io if you'd like and get a headstart. People have prebuilt Dockerfiles laying around for everything (and we have lost of Rust stuff).
We use Dockerfiles kind of like make files. Once you have one that works, you don't need to think about it anymore.
Re: Free Postgres databases for small projects
#215Earlier quoted context omitted.
I actually worry you are undervaluing yourselves. $50 is fine for 10 regions as a data point from where I sit though I wouldn’t object to less
Oh don't you worry. We can extract large sums of money from big companies.
Big places have bet pretty big on docker.
Docker also seems like the quickest option to come out of AWS (ie, ECS or friends) and try fly - so I'd continue chasing a bit of a docker story if you could (even just in docs -> getting going with Docker).
Re: Free Postgres databases for small projects
#216Earlier quoted context omitted.
It's an interesting idea to assume GETs will do no writes, as opposed to POST/PUT/DELETE and route them via middleware, but as an app developer, you need to be very mindful of any updates I suppose... replication delay can also create some weird scenarios I imagine...
That's all solved. We catch readonly errors from Postgres and issue the replay. Preemptively sending a POST to the primary region is an optimization, it works fine without doing that! Replication lag is handled too in the Ruby library we pin requests to the for a few seconds. In our Elixir library, we actually monitor the read replica directly and reroute writes until it's caught up.
I understand roughly what the gem does, but you still need to be aware of it with your app. For example, if every request updates some activity stat, or the last page the user was on (which happens with some apps), you instantly lose pretty much all the benefits, right?
What about redis / sidekiq btw? :)
Re: Free Postgres databases for small projects
#217Earlier quoted context omitted.
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 image though, they start with Phoenix. What you're seeing is a little bit of indecisiveness in how we target the docs.
I just did this with an application I haven't touch in years. The deployment worked on the first try. A few clicks and I had TLS certificates. I'm sold!
I can’t live with this typo. s/touch/touched
Re: Free Postgres databases for small projects
#218Earlier quoted context omitted.
That's all solved. We catch readonly errors from Postgres and issue the replay. Preemptively sending a POST to the primary region is an optimization, it works fine without doing that! Replication lag is handled too in the Ruby library we pin requests to the for a few seconds. In our Elixir library, we actually monitor the read replica directly and reroute writes until it's caught up.
I understand roughly what the gem does, but you still need to be aware of it with your app. For example, if every request updates some activity stat, or the last page the user was on (which happens with some apps), you instantly lose pretty much all the benefits, right? What about redis / sidekiq btw? :)
Ah I see what you're saying! You're basically describing our experience trying to run Discourse. Weirdly, naive, less complicated Rails apps work better multi-region on Fly than mature grownup Rails apps.
We use sidekiq + Fly in a single region with the primary database, and then write to the Redis from other regions asynchronously. It's a good time in Ruby world, I think Ruby 3 will simplify a lot of the weird background work people do.
Ruby 3 will definitely help us solve the problem of gets that do writes for stats or history, since those things can be done async. You can do a little of it now just by spawning a thread and writing the the writable Postgres in the background.
Re: Free Postgres databases for small projects
#219Earlier quoted context omitted.
For 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"[0], they sure have a dearth of documentation on how to deploy an existing docker container. I am not sure if I'm missing something or what, but here's where I looked: * googled 'docker fly' and a blog post that references docker…
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 image though, they start with Phoenix. What you're seeing is a little bit of indecisiveness in how we target the docs.
[deleted]
Re: Free Postgres databases for small projects
#220I had not heard of fly.io but i really appreciate free for side projects! I have a docker setup for .NET core psql app on digital ocean so will be fun to see if i can get a that working with you. Also pricing at a quick glance seems good. Are you running your own servers or using another cloud as the basis?
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.
Thanks I just signed up. Just my opinion but asking for a CC off the bat is friction.
If you need to do that at least have a way to limit spending (by closing services when overspend occurs) and tell me that exists when I sign up.
Hobbiest nightmare is to owe $10k because of a silly mistake. It is why I closed my AWS account (as well as it being too enterprisey to use for hobby).
EDIT: I just read [0] you ask for CC because of crypto miners. Why we can't have 'nice things' I guess :-). I suggest a way to limit spend then, or say "only free services for now".
[0] https://fly.io/blog/free-postgres/#a-note-about-credit-cards