Is Phoenix deployment really that hard?
How much does the Erlang’s great but unexplored hot code reloading complicate the deployment as we know it?
karolsluszniak
2
AstonJ
At DockYard, we transitioned our backend development from Ruby and Rails to Elixir and Phoenix once it became clear that Phoenix better served our clients needs to take on the modern web. As we’ve seen, Phoenix is Not Rails, but we borrow some of their great ideas. We were also delighted to give back in the other direction when Rails announced that Rails 5.0 would be shipping with Action Cable – a feature that takes inspiration from Phoenix Channels.
By @chrismccord
1
karolsluszniak
Phoenix vs Rails: Views and helpers
Here’s an overview, case study and comparison to Phoenix of the V part of Rails MVC as experienced across the years.
3
karolsluszniak
Bootstrapping API project with Phoenix 1.3
Here’s how to create a minimal Phoenix 1.3 setup for API server without HTML, Brunch, Gettext, channels and sessions.
4
nico_amsterdam
Found this blog. Find it interesting:
https://medium.com/@Alexandre_Herve/dynamically-update-phoenix-forms-through-socket-f696d7bb585d#.nodojkavd
5
nico_amsterdam
chvanikoff
A blog post describing mix reph.new task which is very similar to phx.new and based on Phoenix 1.3 installer, but aims to scaffold React/Phoenix-stack based apps.
https://medium.com/@chvanikoff/reph-react-phoenix-app-scaffolding-made-easy-346cddc76838
4
