3 ms·

> Phoenix has no django admin. nuff said. Just curious, did you try Torch or Kaffy? https://github.com/mojotech/torch https://github.com/mojotech/torch https:

> Phoenix has no django admin. nuff said. Just curious, did you try Torch or Kaffy? https://github.com/mojotech/torch https://github.com/mojotech/torch https://github.com/aesmail/kaffy https://github.com/aesmail/kaffy For the ORM and auto-generated DB migrations, I actually prefer the Phoenix way. Ecto makes it much harder to trigger N+1 queries than the Django ORM, and in practice I find the explicit migrations make people actually think about what they're doing and what to index, so the schema is cleaner. But I could see why someone would prefer the Django way, and I'd be curious to see the same kind of system in Elixir.

spapas82 4y ago
I am aware about the libs you mention. Torch is using generators which is a major nono for me, so... Kaffy I always wanted to try but the fact that it's an add on (so I'll get problems when updating) along with the fact that it seems to need a lot of configuration to enable it (as opposed to admin.site.register(Foo,FooAdmin) in Django) made it difficult for me to decide to try it! I agree about the n+1. Its a long debate about how useful it is. I understand it is problematic some times but I'd prefer it any time compared to having to declare all joins on my query. Yes, it had bitten me a couple of times when I was new to Django but nowadays select_related and prefetch_related are like a second nature...
- aaesmail 4y ago
  Creator of Kaffy here. Kaffy was inspired by django's built-in admin. I disagree with one point you mentioned regarding configuration. Kaffy requires less configuration to work out of the box with all your schemas. In django, you do need to to write admin.site.register(Foo) for all your models to be included in the admin interface, where in Kaffy all your schemas/models are included by default. Kaffy also offers things that django admin doesn't like a dashboard, static pages, and scheduled tasks. I suggest you give Kaffy a try and, with your django/phoenix expertise, I'd love to know your feedback.
  - spapas82 4y ago
    Hello, thanks for your comment! I didn't know that Kaffy was inspired from the Django admin, I'll definitely try to use integrate Kaffy in one of my phoenix projects now :)

spapas82 4y ago

I am aware about the libs you mention. Torch is using generators which is a major nono for me, so... Kaffy I always wanted to try but the fact that it's an add on (so I'll get problems when updating) along with the fact that it seems to need a lot of configuration to enable it (as opposed to admin.site.register(Foo,FooAdmin) in Django) made it difficult for me to decide to try it! I agree about the n+1. Its a long debate about how useful it is. I understand it is problematic some times but I'd prefer it any time compared to having to declare all joins on my query. Yes, it had bitten me a couple of times when I was new to Django but nowadays select_related and prefetch_related are like a second nature...

aaesmail 4y ago
Creator of Kaffy here. Kaffy was inspired by django's built-in admin. I disagree with one point you mentioned regarding configuration. Kaffy requires less configuration to work out of the box with all your schemas. In django, you do need to to write admin.site.register(Foo) for all your models to be included in the admin interface, where in Kaffy all your schemas/models are included by default. Kaffy also offers things that django admin doesn't like a dashboard, static pages, and scheduled tasks. I suggest you give Kaffy a try and, with your django/phoenix expertise, I'd love to know your feedback.
- spapas82 4y ago
  Hello, thanks for your comment! I didn't know that Kaffy was inspired from the Django admin, I'll definitely try to use integrate Kaffy in one of my phoenix projects now :)