4 ms·
Oh we're _working_ on it, but we have a ways to go. I can imagine `fly launch` just working for all Elixir apps someday, right now you have to write a Dockerfil
by mrkurt 5y ago
Oh we're _working_ on it, but we have a ways to go. I can imagine `fly launch` just working for all Elixir apps someday, right now you have to write a Dockerfile. People seem to like our guide but I don't want to suggest it's already the easiest possible place to deploy an Elixir app: https://fly.io/docs/getting-started/elixir/ https://fly.io/docs/getting-started/elixir/
That said, our stack does make things Elixir folks need very easy. In particular:
* Private network and built in service discovery mean clustering just works
* You can connect to your private network with WireGuard and then use iex or similar to inspect running Elixir processes: https://fly.io/blog/observing-elixir-in-production/ https://fly.io/blog/observing-elixir-in-production/
* Postgres setup is pretty magical. "fly postgres attach" gets your app all connected and auth'ed to your Postgres cluster.
* And, most importantly, we actually are the best place to run an Elixir app if you're using Phoenix LiveView. You can push your app servers out close to people and make LiveView incredibly responsive: https://liveview-counter.fly.dev/ https://liveview-counter.fly.dev/
- tiffanyh 5y agoThanks so much
- jamra 5y agoIf I were to host Elixir, I don’t think I would opt for docker. This is the one thing that prevents me from trying out fly.io
- pablodavila 5y agoWhy is that? I remember reading about the scheduler not being able to correctly "attach" to each core when using Docker but it seems that's not the case anymore. Is there any other disadvantage you perceive?