News for hackers. Stuff that matters.

A comment on Rapid growth, lessons learned and improvements at Fly.io. Parent comment

Re:Rapid growth, lessons learned and improvements at Fly.io by gen220 on Monday March 06, 2023 @03:09PM (#35046889)
> What I truly want and probably lots of other people too is Flyctl for AWS. The same simplicity to run as fly, but give me something cheap in Virginia or the Dallas.

Pardon the ignorance, is this not the Amplify CLI [1] ?

[1]: https://docs.amplify.aws/cli/

[ Parent | on HN ]
Re:Rapid growth, lessons learned and improvements at Fly.io by pid-1 on Monday March 06, 2023 @03:18PM (#35046997)
No
[ Parent | on HN ]
Re:Rapid growth, lessons learned and improvements at Fly.io by scubbo on Monday March 06, 2023 @03:30PM (#35047140)
Can you elaborate?
[ Parent | on HN ]
Re:Rapid growth, lessons learned and improvements at Fly.io by ctvo on Monday March 06, 2023 @04:44PM (#35048099)
Things that just work and are delight to use and the AWS Amplify CLI are not often mentioned together. The Amplify CLI is a growing collection of poorly thought out, poorly implemented functionality that looks good in demos, but falls apart under any close inspection.
[ Parent | on HN ]
Re:Rapid growth, lessons learned and improvements at Fly.io by Aeolun on Monday March 06, 2023 @07:59PM (#35050096)
I can only assume that if you’ve ever used the amplify cli it makes total sense.

At least that single ‘no’ contained a whole wealth of blood and tears to me.

[ Parent | on HN ]
Re:Rapid growth, lessons learned and improvements at Fly.io by nl on Monday March 06, 2023 @09:47PM (#35050917)
(No the OP)

I like Amplify and use it often. However, it isn't well integrated with "normal" backends, so if you want to keep a backend and frontend deployed together you either have to use their Amplify backend API or work out your own deployment.

[ Parent | on HN ]