So what's the final cost of fly.io + proxy VM + postgres? That was the reason this whole thing started.
How Fly.io and Tailscale Saved Notado
51–60 of 112 posts
Re: How Fly.io and Tailscale Saved Notado
#52No post body was provided.
Re: How Fly.io and Tailscale Saved Notado
#53Quoted post unavailable.
It's a really great product!
Re: How Fly.io and Tailscale Saved Notado
#54Earlier quoted context omitted.
It's interesting to see how being in the same league as kubernetes could either be considered a compliment or an insult depending on who you ask!
K8s is a complexity sinkhole for 99% of companies. It's an insult.
Uh huh here we go. What other tool do you propose for running many containers with dependencies on one another?
Or why should I target a bunch of different cloud APIs to make my tool consumable when I can target one?
Re: How Fly.io and Tailscale Saved Notado
#55Earlier quoted context omitted.
It's interesting to see how being in the same league as kubernetes could either be considered a compliment or an insult depending on who you ask!
K8s is a complexity sinkhole for 99% of companies. It's an insult.
You've inspired me to give it a chance.
Re: How Fly.io and Tailscale Saved Notado
#563000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detai…
[deleted]
Re: How Fly.io and Tailscale Saved Notado
#573000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detai…
No post body was provided.
Re: How Fly.io and Tailscale Saved Notado
#58Earlier quoted context omitted.
“Make any device anywhere part of your own private, secure network.”
Just to further clarify as I've recently gone down the rabbit hole of Tailscale...but isn't the idea that I can make any part of the device running on a private, secure network? In other words, even if I'm connected to a node, I'm still running "on my network", whereas when I connect to a traditional VPN service it just kinda takes all of my traffic and puts it in that same network "space", the biggest difference mea…
By default, and in the most common configuration, the Tailscale “idea” is to intercept all network requests made to a reserved IP range (100.x.x.x) that cannot have public services on it (similar to 192.168.x.x). Each of your devices gets a static IP and can reach any other of your devices using their static IP. All traffic will be encrypted, and it will work really really hard to get through all NAT gateways and firewalls in-between.
As those static IPs are in a reserved range, they will never clash with a public service like a website and Tailscale does not mess with your regular traffic.
You could make things more complicated by setting up exit nodes and exposing subnets, but that’s the general idea. So simple, it’s brilliant for their standard use-case.
Re: How Fly.io and Tailscale Saved Notado
#593000 users? You can save the data on disk and not worry about it. Get a vultr 5 dollar micro instance. I don't know why all these engineer driven businesses focus on the wrong things. You don't need fly.io. Of course they will tell you you need them, I don't blame them. But fly.io or kubernetes should always be done by a migration team which you can hire once you have insane profits. Yes profits, the other tiny detai…
> You can save the data on disk and not worry about it. I one day aspire to have the cajones of ilrwbwrkhv. For the reference of other potential solo devs, if done right, Fly.io will still be cheaper than the Vultr 5 dollar micro instance (or equivalent) with an incomparably better DX.
With the threat of a much higher bill if done wrong. That $2.50 vultr instance provides a lot more like 20 gigs of storage nevermind security of a fixed bill.
You might be able to save a little, you might pay a lot more. Hedge your bet and use vultr.
Re: How Fly.io and Tailscale Saved Notado
#60Earlier quoted context omitted.
Not even the kubernetes cluster, the author eventually is just running multiple processes in a single VM it seems, and scaling vertically using the VM, which of course could have been done on DigitalOcean. However, people do seem to love the fly.io developer experience. It's a testament to fly.io that the auther seemed to enjoy spinning up on fly.io. It's also a testament to DigitalOcean that it wasn't painful or exp…
> Not even the kubernetes cluster, the author eventually is just running multiple processes in a single VM it seems, and scaling vertically using the VM This is an excellent summary! > ... which of course could have been done on DigitalOcean. > However, people do seem to love the fly.io developer experience. It's a testament to fly.io that the auther seemed to enjoy spinning up on fly.io. It could have been done, but…
I’m thinking about a simple blog. Someone convince me that I should use fly.io and caddy and how/why deployment and subsequent blog/post updates would be easy and uncomplicated.