Feature roadmap

[mikey]

Just a suggestion: Would Fly consider publishing/maintaining a (coarse) public feature roadmap?

Mostly, it’d help us build a stronger overall feel for where the platform is going next — a lot of which can be gleaned from discussions here (I love the team’s transparency), albeit bit more piecemeal.

Here’s an example from render.com. Since you’re using discourse, another option is to use the discourse-voting plugin in e.g. a ‘Roadmap’ category, in conjunction with discourse-solved if you want community votes/input.

keep up the good work!

[kurt]

I like this idea, and Render’s is nice! Canny seems like a better take on this problem than most.

What would you vote for if we had one of these?

[mikey]

@kurt

I like this idea, and Render’s is nice! Canny seems like a better take on this problem than most.

Yeah, Canny is one of those “damn, that’s a business?!” products for me. Not knocking them - more like jealous of their low-complexity revenue stream…

@kurt

What would you vote for if we had one of these?

To be honest, not really sure! I suppose that’d be the fun of it. Only a couple small things I’m looking for at the moment: Rollback API/UI. Logs stream API. And I’d use a HTTP-to-HTTPS redirector at the LB.

[lubien]

@mikey

Logs stream API

Would this be perhaps what you want?

Fly Logs over NATS

Hi folks! I’ve been working on exposing a NATS endpoint for logs recently and it’s finally ready for some people to try out! I’ve written a proxy that lets you connect a NATS client to nats://[fdaa::3]:4223 from inside a fly app, using an organization slug (available from fly orgs list) as the username and a personal access token as the password, and subscribe to your fly logs to do what you please with them. The subject schema is logs.<app_name>.<region>.<instance_id> and you can use all the n…

[mikey]

@lubien

Would this be perhaps what you want?

That… definitely looks like it! Thanks!