←back to thread

1226 points bishopsmother | 1 comments | | HN request time: 0.202s | source
Show context
samwillis ◴[] No.35046486[source]
Fundamentally I think some of the problems come down to the difference between what Fly set out to build and what the market currently want.

Fly (to my understanding) at its core is about edge compute. That is where they started and what the team are most excited about developing. It's a brilliant idea, they have the skills and expertise. They are going to be successful at it.

However, at the same time the market is looking for a successor to Heroku. A zero dev ops PAAS with instant deployment, dirt simple managed Postgres, generous free level of service, lower cost as you scale, and a few regions around the world. That isn't what Fly set out to do... exactly, but is sort of the market they find themselves in when Heroku then basically told its low value customers to go away.

It's that slight miss alignment of strategy and market fit that results in maybe decisions being made that benefit the original vision, but not necessarily the immediate influx of customers.

I don't envy the stress the Fly team are under, but what an exciting set of problems they are trying to solve, I do envy that!

replies(20): >>35046650 #>>35046685 #>>35046754 #>>35046953 #>>35047128 #>>35047302 #>>35047334 #>>35047345 #>>35047376 #>>35047603 #>>35047656 #>>35047786 #>>35047788 #>>35047937 #>>35048244 #>>35048674 #>>35049946 #>>35050285 #>>35051885 #>>35056048 #
satvikpendem ◴[] No.35047603[source]
I'm going to plug Coolify, an open source Heroku alternative (with Docker support too) that I'm using on a cheap $5 Hetzner server which is a lot cheaper than the equivalent Fly or Render etc service, and it really doesn't have much upkeep from me even if you add in the time setting up the server initially, which is like an hour, and afterwards, it Just Works™.

https://coolify.io

replies(2): >>35048654 #>>35048955 #
notpushkin ◴[] No.35048654[source]
Dokku is also nice and battle-tested: https://dokku.com/

And may I also plug Lunni, a self-hosted Docker Swarm-based PaaS I'm working on right now: https://lunni.dev/

Both work pretty well on $5 servers.

replies(5): >>35048720 #>>35049033 #>>35049034 #>>35050171 #>>35050962 #
Aeolun ◴[] No.35050171[source]
Personally I use portainer for basically the same thing. My only real requirement was that I could easily copy-paste in docker-compose files and have it just work.

I use caddy as the proxy, since I found the traefik configuration absolutely incomprehensible. Now I use only 2 labels to proxy instead of 15.

replies(1): >>35058073 #
1. notpushkin ◴[] No.35058073[source]
Caddy is nice, I've been playing around with it too and I love it. Perhaps we can port Lunni to use it, too.

Portainer is also cool – we're using it internally as an API, actually! I've been using it before starting Lunni and my only objection is the UI. Portainer is kinda like a Swiss army knife for containers, but with this power comes the complexity, too.

For example, to see service logs, you have to pick an environment, then go to Stacks, find your stack, find the service you need, open it and then you'll see the service logs button. In Lunni, you open your stack right from the dashboard and click logs button right beside your service name: https://u.ale.sh/lunni-screenshot-logs-button.png