aesmail

Hello guys,

I have finally made it. I created an admin interface for a framework. It’s been on my todo list for years and with the current global pandemic, I kind of had the mindset and time to work on a few things on that list.

The package is in its very early stages, but I started using it for my own projects.
The following is part of the README file.

Kaffy

Extremely simple yet powerful admin interface for phoenix applications

Why another admin interface

Kaffy was created out of a need to have a minimum, flexible, and customizable admin interface
without the need to touch the current codebase. It should work out of the box just by adding some
configs in your config.exs file (with the exception of adding a one liner to your router.ex file).

A few points that encouraged the creation of Kaffy:

Taking contexts into account.
- Supporting contexts makes the admin interface better organized.
Can handle as many schemas as necessary.
- Whether we have 1 schema or 1000 schemas, the admin interface should adapt well.
Have a visually pleasant user interface.
- This might be subjective.
No generators or generated templates.
- I believe the less files there are the better. This also means it’s easier to upgrade for users when releasing new versions. This might mean some flexibility and customizations will be lost, but it’s a trade-off.
Existing schemas/contexts shouldn’t have to be modified.
- I shouldn’t have to change my code in order to adapt to the package, the package should adapt to my code.
Should be easy to use whether with a new project or with existing projects with a lot of schemas.
- Adding kaffy should be as easy for existing projects as it is for new ones.
Highly flexible and customizable.
- Provide as many configurable options as possible.
As few dependencies as possible.
- Currently kaffy only depends on phoenix and ecto.
Simple authorization.
- I need to limit access for some admins to some schemas.
Minimum assumptions.
- Need to modify a schema’s primary key? Need to hide a certain field? No problem.

GitHub link
Hex package

All critique, criticism, PRs, and feedback are welcome.

97 comments

/phoenix #ecto #library #admin-tools #kaffy

77 25862 97

2025-09-20 21:58:54 UTC

Showing Posts 97 to 88

Show Best Posts
Show All (oldest first)
Show All (newest first)

cgraham

Does Kaffy work with Phoenix 1.8? Couldn’t figure out how to do it. Thx!

Post #100

Stefano1990

There is ashadmin.

Post #99

brightball

I wonder how difficult it would be to use Kaffy with an application built with Ash?

Post #98

Faheemvc

I am curious to know how kaffy is validating forms with changeset and is it possible to customize the validation with different changesets in schema in admin modules

note: in my application context, admin module name is different from schema name

enterprise: [
        name: "Enterprise",
        resources: [
          plan: [
            schema: WraftDoc.Enterprise.Plan,
            admin: WraftDocWeb.PlanAdmin
          ],
          enterprise_plan: [
            schema: WraftDoc.Enterprise.Plan,
            admin: WraftDocWeb.EnterprisePlanAdmin
          ]
        ]
      ],

in WraftDocWeb.EnterprisePlanAdmin added
def create_changeset(schema, attrs) do
Plan.custom_plan_changeset(schema, attrs)
end

in plan admin with plan schema validations and everything works fine, in enterprise plan admin form validation not working, in case any changeset errors it raises error and not displaying the errors at form fields, if changeset is valid will create.

Post #97

antonioparisi

hi, @aesmail - are you still maintaining Kaffy?
I’m curious to know the progress of the has_many association forms feature (if any)

regards

Post #95

aesmail

This is an important announcement for anyone using Kaffy v0.10

Please note that Kaffy v0.10.1 introduced a bug that ignored all admin modules.

v0.10.1 was released on Monday, October 9, 2023 at 11:57am GMT and v0.10.2 (which fixed the issue) was released at 12:49pm GMT (the time period between the two releases is about 52 minutes).

So if you deployed within this time period, please update Kaffy and deploy again.

Version v0.10.1 has been marked as retired and is no longer available on hex.

Apologies for any issues that this might have caused some of you.

Post #94

jarlah

in v0.10 rc2, i love that you fixed an issue with many_to_many causing kaffy to crash its not shown or is any value to kaffy, but i can use it in the rest of code

Post #93

jarlah

great work lazy mans tool for when you dont want to use up your time fiddling with creating UIs when it might not even be used in the end…

Post #92

aesmail

You can always do {:kaffy, "~> 0.10.0-rc.0"} to test it out.
I don’t think things will change as long as there are no serious issues.
The plan is to release 0.10.0-rc.1 a week from now with a few planned minor changes, and 0.10.0 a week after that.

Post #91