thojanssens1
How to have a separate admin section?
I’m building my first Phoenix app and need a little guidance.
Say I build a quiz maker.
- Admin users may create questions and answers;
- Visitors of the website can answer the questions.
I ran the following command to create my first context:
mix phx.gen.html Quiz Question questions text:string
But what confuses me, is that I will have two clearly distinct sections of my website, with two different layouts: a layout and templates for admins, and a layout and templates for the visitors.
Most of these generated files such as the templates to list the questions, create/edit/delete a question, and so on should only be accessible by an admin user.
Also, the template to view a question show.html.eex will be different for an admin and a visitor: the visitor will have a nicely displayed question (with different html), while the admin will have a rather raw template, using the same layout as the layout used for listing questions and editing questions.
All of the admin templates will have a basic layout, while the templates for the visitors will have a layout with a nicer design.
The command above generates for exemple:
lib/quiz_maker_web/templates/question/show.html.eex
lib/quiz_maker_web/templates/question/form.html.eex
...
While I need something like:
lib/quiz_maker_web/templates/admin/question/show.html.eex
lib/quiz_maker_web/templates/admin/question/form.html.eex
lib/quiz_maker_web/templates/guest/question/show.html.eex
...
I think my requirement is a pretty basic one, but I don’t know the best way to achieve it. Any help is very much appreciated!
Marked As Solved
idi527
You can have “scoped” controllers like
defmodule YourAppWeb.Admin.QuestionController do
end
this would make phoenix use lib/quiz_maker_web/view/admin/question_view.ex and look in lib/quiz_maker_web/templates/admin/ for the templates.
Also Liked
jeremyjh
Hi, you can make a separate pipeline in which you specify a different template for the layout, and then use that pipeline in the scope that contains the admin routes.
For example, define a separate layout in admin.html.eex, then configure your router something like:
pipeline :admin_pages do
plug(:accepts, ["html"])
plug :put_layout, {MyAppWeb.LayoutView, "admin.html"}
end
scope "/admin", MyAppWeb, as: :admin do
pipe_through(:admin_pages)
get("/", AdminController, :index)
end
Any pages served under /admin will get the admin layout.
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"