TL;DR flyctl v0.2.88 and @flydotio/dockerfile v0.5.8 introduce Meteor support!
Just in time for the much anticipated Meteor 3.0 release which modernizes the framework with Node.js LTS compatibility and more. I think this release is going to breathe new life into the community which has arguably fizzled over the past few years with the explosion of fancy new JS frameworks (which we also support 
).
Meteor is the OG “real-time” framework — you get a lot of really cool features for free that make it hard to beat for a one-man-band or small dev shop.
Visit our docs for a complete deployment walkthrough: Run a Meteor App · Fly Docs
A note about load-balancing
In the days before Fly.io and when Meteor was still the hotness, the two main deployment questions that came up again and again were:
- Do WebSockets work with this?
- Are Sticky Sessions supported?
The answer to the first is easy: yes. The second is more complex. It’s unclear to me how important or relevant sticky sessions (AKA session affinity) is with the modern iteration of Meteor. If you reach a scale where this matters, get in touch with us. But a safe option is to run only one Machine per region (if you’re only running in one region, run a single Machine with a standby). Alternatively, you could run an nginx proxy with IP hashing.
With that said, there is some interesting work with the Fly Proxy coming down the pipe that might deem this a non-issue.
Demo
Simple Tasks is a fun, open-source Meteor app that has been upgraded to Meteor 3.0 — give it a whirl and bask in the realtimey goodness: https://meteor-demo.fly.dev/
Cheers!