The very first screenshot on the Github shows a listing of database entries and such. This is not what LiveDashboard does.
lawik
Nerves Core Team
KP123
To be fair PLD is extensible so it’s something it can do. So to ask my question a different way why would I use this instead of what’s included out of the box with Phoenix?
0
cmo
KP123
But what does this include? Live Dashboard is just some already designed live views. I can add arbitrary pages to LiveDashboard. I linked to the documentation explaining how above. Once you add a new page to LiveDashboard it’s just a regular LiveView, meaning I can make it display any content I want, including all of the content that Backpex displays in its documentation images. The difference is that out of the box LiveDashboard comes configured with a ton of useful pages and Backpex requires me to rebuild all of this functionality (as stated by the author of the lib). If Backpex requires me to write integration code anyway what do I gain by bringing in this library over just adding a new page to LiveDashboard and writing the same integration against a vanilla LiveView?
1
cmo
So you have LiveDashboard setup and you want to create an admin backend. You either build the admin backend yourself, which is perfectly fine to do, or you add one of the several admin backend libraries so some of the the work is done for you. Just because you install one of these libs doesn’t mean you remove LiveDashboard and try to rebuild it’s functionality. You also might not want everyone who has access to the admin backend to see the rest of LiveDashboard. It’s not an either/or situation, both can exist side by side and do different things.
1
KP123
This definitely makes it clearer why I’d consider using something like this. I’m still not sold on the other reason but I’m someone that prefers to write a little bit of boilerplate to avoid taking on new dependencies.
A second thing I learned from this is that prompt engineering is not in my future
1
egeersoz
ghannam80
I have checked the high level road map and per my understanding of what Backpex should provide then I think supporting the below would be required besides dual control requested earlier :
- Audit records changes “Might be enhanced even to allow some kind of notes or attachment for change reason”.
- Filter user access or rights based on profile
- Mask sensitive data if user profile does not allow full display like card number or balance in case of payment applications as an example.
0
zhangzhen
Unfortunately, Backpex does not support Ash at the moment.