mix_install_examples VS ecto_sqlite3

Ya, it's fair, it's a common complaint! Though the size of the generated files is nothing compared to Rails :D

You're right that phx_new does count too. It's a bit misunderstood that Phoenix is actually closer to a micro-framework like Flask than it is a full-fledged solution like Django or Rails. What takes it up to their level is `mix phx.new`, so your argument is more on point than I initially thought. The LiveView issue tracker even provides a single-file version of a Phoenix app to re-create your issue in [0]. As you can see, it's not as simple as something like Flask, but not as complex as the generator does.

Again, great article and happy to have you aboard ;)

Also, if you want an auth solution without code generation, there is Pow [1]

[0] https://github.com/wojtekmach/mix_install_examples/blob/main...

- learning how to compute the checksum of the internal content of a zip file https://github.com/etalab/transport-site/blob/master/scripts...

As mentioned in the article, I can definitely recommend to check out https://github.com/wojtekmach/mix_install_examples which has a long list of examples.

Streaming ChatGPT via SSE in Elixir: https://github.com/wojtekmach/mix_install_examples/pull/22#i...

love elixir. hate Mix.

it's like using Maven or npm all over again. but even worse because it generates a lot of code.

it creates disposable projects by design. No way to keep track of what to change when mix create outputs something different next year.

and now things like https://github.com/wojtekmach/mix_install_examples/blob/main... where is ecto even installed? download from where? so annoying this trend.

Like others have told you, Phoenix doesn't really add much complexity / fat / weight. In terms of complexity, if you don't want to use phx_new to boostrap the project here's a sample of using Phoenix LiveView in a single script file: https://github.com/wojtekmach/mix_install_examples/blob/main/phoenix_live_view.exs

If you want to play around with Ecto in isolation, you can (thanks to `Mix.install/2`) work in single-files, all containing the migrations, the schemas and configuration.

Check-out this repository for an example (and other single-file examples):

https://github.com/wojtekmach/mix_install_examples/blob/main...

You could adapt this script and replace Postgrex with the ecto_sqlite3 adapter:

https://github.com/wojtekmach/mix_install_examples/blob/main...

https://github.com/elixir-sqlite/ecto_sqlite3

One of the most appealing features of Elixir for me was that it has a self-contained ecosystem. All you need to deploy a production-ready application is the application itself and PostgreSQL. No need for Redis, k8s, Kafka, Nginx, and all that stuff. But can we also go without PostgreSQL (and without losing the power of SQL)? For my first Elixir project, I picked SQLite which doesn't require running a separate service and works great with Ecto, thanks to ecto_sqlite3. And imagine my disappointment when Phoenix Live Dashboard didn't show any fancy stats as it does for PostgreSQL.