inertia_phoenix VS real world example app

Maintained by Devato

yea it was a godsend that fit exactly what I wanted. I don't want to build an API and I don't want nodejs as my backend. It just injects props for me and then I can do all the cool phoenix things like use channels (i make heavy use of websocket backed svelte stores). Here's the plug you'll need in case you haven't found it. https://github.com/devato/inertia_phoenix let me know if any questions as I think this combo is really powerful and would be happy to assist in it's usage.

After that, you're left with everything else in your application, much of which is interrelated on the data level. Using this repo as an example, you find that it has Accounts and then Blog as the primary namespaces (which make sense), which then leaves you with blog.ex which is a file containing a ton of database reading/writing/helper functions for all these different entities in the namespace (this is how the generators will also scaffold things, continuing to pile on the functions). It feel strange to me to have one giant file that forever grows proportional to the size of the namespace with so many concerns. Is it a good idea to split these things out (particularly when the ecto models aren't responsible for database queries in Pheonix) or am I just thinking about this the wrong way??

Getting Id token - here is some example: https://github.com/gothinkster/elixir-phoenix-realworld-example-app