Does anyone know any good example of web applications without Phoenix? I think Elixir is so damn simple, but every time I create a Phoenix project is just too much. I just want to do something with Ecto, Plug, and Htmx.

I‘d suggest differentiating phoenix the library from code, which is generated by phoenix generators. Because most of what the latter provides is not set in stone as all. It‘s one way of doing things, which caters best to the usecase of powering crud generators for people trying to quickly scaffold …

@wojtekmach ’s repository of single-file apps might be very helpful to you: https://github.com/wojtekmach/mix_install_examples/blob/727e0a70aeb194593eac913afc224c5c0e0f09ea/plug_cowboy.exs It was for me. [image] pmjoe: I think Elixir is so damn simple, but every time I create a Phoenix project…

[image] dimitarvp: I simply wish we had PhoenixLite or something This is mentioned often and I wonder if simply highlighting the --no-* options in the getting started guide would help, because a lot of Phoenix is optional: --no-assets - equivalent to --no-esbuild and --no-tailwind --no-dash…

This sentiment surely comes up regularly, but having seen people attempt this over the years I‘m not sure skipping phoenix (the library) is worth it. Plug for simple stuff can be quite simple code and less files, but on the other hand any more advanced stuff will need you to write more code than yo…

[image] mayel: So apart from adding a --no-telemtry flag I’m not sure how much lighter it could reasonably get while still being sensible? I am strictly focusing on amount of files, not the removal of features, some of which are critical for most commercial projects (like HTML/templating and …

[image] LostKobrakai: This sentiment surely comes up regularly, but having seen people attempt this over the years I‘m not sure skipping phoenix (the library) is worth it. I agree. Even though the amount of files to me seem too much I’ve also experienced first-hand how extremely useful Phoeni…

[image] mayel: I wonder if simply highlighting the --no-* options in the getting started guide would help, because a lot of Phoenix is optional I went ahead with a simple PR: clarify what's optional in phx.new by mayel · Pull Request #5783 · phoenixframework/phoenix · GitHub

My point is that with Phoenix I feel that the framework becomes your application. If I’m not mistaken Dave Thomas has talked a lot about this. Phoenix for me is the outer layer of an application, it’s the API or how it communicates with the outside world.

[image] LostKobrakai: It‘s one way of doing things, which caters best to the usecase of powering crud generators for people trying to quickly scaffold apps. You‘re free if not encouraged to adjust those things to fit whatever else you need. Sounds like a good opportunity to upstream some more…

Yes, I think that’s it. The library is simple and composable while the generator really feels too much and complex. Instead of playing directly with plug I’ll try to just import the phoenix libraries individually.

Good example of plug based web application

Questions & Help Questions

dimitarvp April 14, 2024, 1:28pm 11

Sounds like a good opportunity to upstream some more generators for other cases, then.