{"repo":"petalframework/petal_boilerplate","free":true,"listed":false,"github":"https://github.com/petalframework/petal_boilerplate","clone":"git clone https://github.com/petalframework/petal_boilerplate.git","description":"Phoenix + Tailwind + Petal Components Boilerplate","language":"Elixir","stars":175,"topics":["elixir","phoenix","phoenix-framework","tailwindcss"],"license":"MIT","category":"saas-starters-boilerplates","readme_excerpt":"Petal Boilerplate A clean install of the Phoenix 1.7 (RC) along with: - Alpine JS - using a CDN to avoid needing node modules - 🌺 Petal Components Library - Maintained and sponsored by Petal Framework Get up and running Optionally change your database name in dev.exs . 1. Setup the project with mix setup 2. Start Phoenix endpoint with mix phx.server or inside IEx with iex -S mix phx.server 3. Now you can visit localhost:4000 from your browser. Phoenix 1.7 generators 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: 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. Renaming your project Run mix rename PetalBoilerplate YourNewName to rename your project. You can then remove {:rename project, \" 0.1.0\", only: :dev} from your mix.exs file.","default_branch":null,"files":null,"tree":[],"storefront":"/r/petalframework","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/petalframework/petal_boilerplate/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}