Docs / Ecosystems

Elixir

Name: Better Fullstack
Availability: InStock

Phoenix scaffolds with Ecto SQL, PostgreSQL-ready config, REST or Absinthe, realtime, jobs, tests, and deployment files.

Elixir projects generate Phoenix applications that follow Mix and Phoenix conventions. Choose Elixir options for LiveView, Ecto SQL, auth, APIs, realtime, jobs, testing, quality, and deploy files.

Prerequisites

Elixir and Erlang/OTP compatible with Phoenix 1.7.
PostgreSQL when using ecto-sql, phx-gen-auth, or oban.
Git if you want repository initialization.

Scripted example

npm create better-fullstack@latest my-phoenix-app -- \  --ecosystem elixir \  --elixir-web-framework phoenix-live-view \  --elixir-orm ecto-sql \  --elixir-auth phx-gen-auth \  --elixir-api absinthe \  --elixir-realtime presence \  --elixir-jobs oban \  --elixir-http req \  --elixir-json jason \  --elixir-observability telemetry \  --elixir-testing ex_unit \  --elixir-quality credo \  --elixir-deploy docker \  --ai-docs none \  --no-install \  --no-git

Elixir categories

Category	Values
Web framework	`phoenix` `phoenix-live-view`
Persistence	`ecto-sql` `none`
Auth	`phx-gen-auth` `ueberauth` `guardian` `none`
API	`rest` `absinthe` `grpc` `none`
Libraries (multi-select)	`broadway` `nx` `none`
Realtime	`channels` `presence` `pubsub` `live-view-streams` `none`
Jobs	`oban` `quantum` `none`
HTTP	`req` `finch` `none`
JSON	`jason`
Email	`swoosh` `none`
Caching	`cachex` `nebulex` `none`
Observability	`telemetry` `opentelemetry` `prom_ex` `none`
Testing	`ex_unit` `mox` `bypass` `wallaby` `none`
Quality	`credo` `dialyxir` `sobelow` `none`
Deploy	`docker` `fly` `gigalixir` `mix-release` `none`

Compatibility notes

Elixir options only apply with --ecosystem elixir.
Phoenix and Phoenix LiveView are standalone Elixir web frameworks; TypeScript frontend and backend options are ignored.
phx-gen-auth and Oban require Ecto SQL because the generated code needs a Repo and migrations.
Oban targets PostgreSQL-backed Ecto SQL projects.
LiveView streams require phoenix-live-view.
A few schema-level choices are intentionally rejected by the graph validator until matching templates exist: ecto, ueberauth, guardian, nimble-options, nebulex, opentelemetry, prom_ex, mox, bypass, wallaby, fly, and gigalixir. The CLI and builder surface those as unsupported-tool messages rather than generating partial Phoenix code.

Generated behavior

The project includes mix.exs, Phoenix config, router, endpoint, controllers, tests, .env.example, and setup notes.
Ecto SQL selections include a Repo, migrations, schema/context code, and PostgreSQL config.
Optional selections add working Phoenix files for LiveView, Channels/Presence, Oban or Quantum jobs, Absinthe schema/resolvers, Req/Finch HTTP clients, Swoosh mailer, Cachex, Dockerfile, and release config.