
If you've used Ruby on Rails or Laravel in php you will be familiar with app generators. To make the inital steps go faster, we'll lean on Phoenix's generators to build the app and add initial scaffolding.
#Rails liveview install#
If you are on linux, you will need to install inotify-tools to enable Phoenix's live reload feature.Īt this point you should be ready to start building the application.Postgres is the default database for Phoenix, but you can specify others at application creation time.mix archive.install hex phx_new to install or update Phoenix.mix local.hex to install or update the package manager for Elixir.Each linux distro has it's own method so check the referenced link for your distro. brew install elixir (for mac) or cinst elixir (for windows with Choclatey).If you don't have time to head over there and follow along, here are the steps at the command line. The documentation website is generated out of the source of the various projects, so it stays fairly accurate and up-to-date. It is a first class citizen in community-supported libraries. Documentation is one of the many great things about the Elixir community. If you haven't worked with Phoenix before, I recommend following the Phoenix Installation guide.

I picked this task, not because I know what I'm doing, but because I want to explore the edges where frontend SPA widgets interact with the realtime features of LiveView. In this post we will do all the setup work of starting a new Phoenix LiveView app, adding a Document context and doing the initial editor integration. As promised in the first article of this series we are about to embark on a journey to build a collaborative rich text editor widget.
