A clean install of the Phoenix 1.7 (RC) along with:
- Alpine JS - using a CDN to avoid needing
node_modules
- ๐บ Petal Components Library
Optionally change your database name in dev.exs
.
- Setup the project with
mix setup
- Start Phoenix endpoint with
mix phx.server
or inside IEx withiex -S mix phx.server
- Now you can visit
localhost:4000
from your browser.
The CRUD generators (eg. mix phx.gen.live
) will produce code that doesn't quite work. Basically, they will use components defined in core_components.ex
that we have renamed due to naming clashes with Petal Components.
To fix, simply do a find and replace in the generated code:
Replace `.modal` with `.phx_modal`
Replace `.table` with `.phx_table`
Replace `.button` with `.phx_button`
This should make it work but it'll be using a different style of buttons/tables/modal to Petal Components. To work with Petal Components you will need to replace all buttons/tables/modal with the Petal Component versions.
Petal Pro currently comes with a generator to build CRUD interfaces with Petal Components. You can purchase it here.
Your app module is currently called PetalBoilerplate
. There is a script file included that will rename your project to anything you like in one go.
Open the file rename_phoenix_project.sh
and read the instructions at the top.