Admin backends for Phoenix

We got away with https://elements.heroku.com/addons/adminium for now.

I tend to roll my own. Perhaps this could be the start of a collaboration of sorts on this forum.

What about ExAdmin? It looks pretty good?

Demo here: http://demo2.exadmin.info/admin

Hello,
there is another one called: torch

edited: (I forgot this one…!)

2. talon
   It’s the new version of ExAdmin and proposed by @smpallen99 as a solution of ExAdmin’s lack

Hello there,
concerning administration Panel concept, I’ll recommend reading the @chrismccord 's way… Writing Web-facing features…

Applications with “users” are naturally heavily user driven. After all, our software is typically designed to be used by human end-users one way or another. Instead of extending our Accounts.User struct to track every field and responsibility of our entire platform, it’s better to keep those responsibilities with the modules who own that functionality. In our case, we can create a CMS.Author struct that holds author specific fields as it relates to a CMS. Now we can place fields like “role” and “bio” here, where they naturally live. Likewise, we also gain specialized datastructures in our application that are suited to the domain that we are operating in, rather than a single %User{} in the system that has to be everything to everyone.

But knowing that the ideas may differ, what are your thoughts about his opinion/point of view?

What are people using these days? Seems like most of the mentioned projects in this thread, is not maintained any longer.

Currently the two most downloaded are:

Ex Admin - An Elixir Phoenix Auto Administration Package.
torch - Rapid admin generator for Phoenix

Full list here.

As i can see ExAdmin is not maintained any more?
Torch last commit was 4 month ago. And in general it doesn’t look like complex solution.

I’m looking forward to use Phoenix in my next project, but admin panel is really needed.
What to use, any advice?

I’m working on an admin backend inspired by torch and ex_admin. The core component is a library to generate ecto queries dynamically from phoenix params (also written by me) which I haven’t released yet. I can’t guarantee the API stability of this library yet, though…

If people are interested in trying it I might publish it (as super alpha software) . It’s already quite functional, actually.

It makes heavy use of generators, so it’s closer to torch than ex_admin. IMO, the main advantage over torch is that the generated code (especially the templates) are a bit cleaner and easier to extend, and I think it supports a little more features.

I tried both Torch and ExAdmin but didn’t like either so I built the admin interface using the Phoenix generators. It’s been really easy to work with, and so far it’s felt like the better option to opt for. This was done in an umbrella app setup with multiple Phoenix apps.

You can slap on a Bootstrap admin template, add a user authentication library, and have it up and running in no time.