4 ms·

Hi Chris Excited to see in this thread you joining fly.io Can talk about what (if) any plans exist to make deploying Phoenix apps at fly easier. Said another

Hi Chris Excited to see in this thread you joining fly.io Can talk about what (if) any plans exist to make deploying Phoenix apps at fly easier. Said another way, I’d love to click a button to deploy my app to be (a) globally distributed, (b) managed global database, (c) managed operating systems, (d) managed dns. Basically heroku for Phoenix (and more)

mrkurt 5y ago
Yes! What you're describing is important, and roughly matches what we want for all apps. Managing apps + databases across multiple regions should be as simple as `fly region add syd`. This takes like 5 steps right now, it should take one. We're also improving the Phoenix deploy process. I don't like it when people have to see Dockerfiles. Modern app deployment needs frameworks and infrastructure to work together. Our Elixir deployment doc (https://fly.io/docs/getting-started/elixir/ https://fly.io/docs/getting-started/elixir/) will someday be replaced with, hopefully, "mix phx.deploy".
- alberth 5y ago
  That’s really exciting to hear. A few follow-ups: a. Will pre-prod environments be included in those plans you outlined above (eg Dev, Test, Stage) b. Any plans to make it easier on Developers to have local/remote environments for development? (Eg GitHub Codespaces) c. Do customers typically also use 3rd party security offerings like Cloudflare in conjunction with fly.io - or do you see more customer just using fly.io without any additional protection? d. One thing that Cloudflare Workers does that’s interesting is that it deploys your webasm code to every pop/region they have & them orchestrate the communication between the regions to keep data consistent. Is similar functionality on roadmap? e. Any rough order of magnitude on timing for what you described?
  - mrkurt 5y ago
    Our database roadmap is: 1. Self service snapshots/restores 2. Get it out of beta 3. Single command database and apps management My time estimates are always wrong, but that feels like 3 months. The really slick Phoenix release process is going to happen in parallel but it's hard to say when.

mrkurt 5y ago

Yes! What you're describing is important, and roughly matches what we want for all apps. Managing apps + databases across multiple regions should be as simple as `fly region add syd`. This takes like 5 steps right now, it should take one. We're also improving the Phoenix deploy process. I don't like it when people have to see Dockerfiles. Modern app deployment needs frameworks and infrastructure to work together. Our Elixir deployment doc (https://fly.io/docs/getting-started/elixir/ https://fly.io/docs/getting-started/elixir/) will someday be replaced with, hopefully, "mix phx.deploy".

alberth 5y ago
That’s really exciting to hear. A few follow-ups: a. Will pre-prod environments be included in those plans you outlined above (eg Dev, Test, Stage) b. Any plans to make it easier on Developers to have local/remote environments for development? (Eg GitHub Codespaces) c. Do customers typically also use 3rd party security offerings like Cloudflare in conjunction with fly.io - or do you see more customer just using fly.io without any additional protection? d. One thing that Cloudflare Workers does that’s interesting is that it deploys your webasm code to every pop/region they have & them orchestrate the communication between the regions to keep data consistent. Is similar functionality on roadmap? e. Any rough order of magnitude on timing for what you described?
- mrkurt 5y ago
  Our database roadmap is: 1. Self service snapshots/restores 2. Get it out of beta 3. Single command database and apps management My time estimates are always wrong, but that feels like 3 months. The really slick Phoenix release process is going to happen in parallel but it's hard to say when.