flyctl init
Error: unknown command "init" for "flyctl.exe"
Run 'flyctl.exe --help' for usage.
It seems that the command is replaced with launch. But why don’t you make it an alias to it? Or at least suggest which is it replacement? Also, you should update the command in your blog posts, such as this one: Deno on Fly · The Fly Blog
flyctl.exe version 0.4.74
Yes, launch would be the equivalent command at this point.
It looks like flyctl init has been deprecated for about 5 years at this point. I expect the reason we didn’t alias it to fly launch back then is that the init command actually did different things compared to launch, so aliasing it would have broken user’s expectations at the time.
While we work hard to keep commands referenced in the docs and our blueprint guides accurate and up to date, blog posts are best treated as accurate to when they were published (2020, in the case of that deno one) but not evergreen.
if so, then when users use init, why not suggesting launch? That way, your past blog posts doesn’t make confusion for users
On the internet, blog posts tend to be frozen in time; some folks consider it bad form to retroactively change a post, as it looks like one is editing history. Some blogs will render an on-page warning if it is viewed more than a couple of years after it was written.