- How do I install the TALL stack in Laravel with a single command?
- ralphjsmit/tall-install adds an Artisan command that pulls in Tailwind CSS, Alpine.js, and Livewire, wires up the frontend assets, and applies opinionated presets so you can start building reactive Blade interfaces right away. It is meant for new, greenfield Laravel projects rather than retrofitting the stack onto an existing app. Because it is a development-time scaffolder, it should never be installed as a production dependency.
- Does ralphjsmit/tall-install support Laravel 11 or Laravel 12?
- No. The last release shipped on 29 April 2022 and the repository is archived, so the generated baseline targets Laravel 9-era conventions with Livewire 2, Tailwind 3, and PHP 8.1. Running it against a Laravel 11 or 12 skeleton can fail Composer resolution or, worse, produce half-wired output such as a stale asset pipeline, incomplete auth scaffolding, or duplicated frontend toolchains.
- Which packages does tall-install install by default?
- It preselects an opinionated set of packages that typically covers authentication scaffolding, admin tooling, testing, code formatting, and static analysis. The exact list is baked into the archived 1.4.0 release, so review the installer source and compare every choice against your own dependency allowlist before running it. Anything it adds automatically becomes something you own.
- Can I run tall-install non-interactively in CI or Docker?
- Only partially. Release 1.4.0 explicitly made the TallInstall command interactive, so it expects a TTY and can hang or silently pick unexpected defaults inside Docker builds, CI pipelines, or unattended bootstraps. For reproducibility, run it once in a sandbox on a pinned toolchain and commit the resulting composer.lock and package-lock.json instead of invoking it in automation.
- Is ralphjsmit/tall-install safe to use in production?
- It is a one-shot dev-time scaffolder and must never become a runtime dependency in a deployed application. The bigger production concern is that the generated code carries 2022 dependency assumptions with no upstream security patches, so every CVE, framework upgrade, and Livewire migration becomes your team's responsibility.
- What Laravel, PHP, Node, and Livewire versions does tall-install target?
- The pinned dependencies were published in April 2022 and target roughly PHP 8.1, Laravel 9, Livewire 2, Tailwind 3, and the Node tooling of that era. Verify that the resulting lock files still resolve cleanly today, because PHP 8.3+, Laravel 11 or 12 skeletons, and Livewire 3 can break Composer resolution or leave the frontend build half-configured.
- Should I use tall-install or the official Laravel starter kit?
- For most teams, the official Laravel starter kits plus a thin internal template deliver the same time-to-first-demo with far less risk. tall-install is most valuable as a reference checklist for the prompts, configuration steps, package choices, and asset wiring you want in your own TALL golden path.
- Is ralphjsmit/tall-install still maintained?
- No. The repository is archived, the last release was 1.4.0 on 29 April 2022, and with roughly 42 stars and zero dependents there is effectively no external reliability evidence. The MIT licence removes legal friction and permits a fork, but a fork needs a named maintainer, a pinned commit, and an explicit upgrade plan before it touches a product roadmap.
- How do I install ralphjsmit/tall-install with Composer?
- It is published on Packagist as ralphjsmit/tall-install, so you add it with Composer in a throwaway or sandbox project and then run the provided Artisan command. Keep it out of the require section and out of any deployed environment, since it only exists to generate the initial scaffold.
- Can I use tall-install in an existing Laravel application?
- It is designed for greenfield Laravel applications committed to Blade, Livewire, Tailwind, and Alpine, and it does not fit existing applications, non-TALL stacks, or repositories with a curated dependency allowlist and security gating. Running it against an established codebase risks duplicated frontend toolchains, conflicting package versions, and broken asset compilation that only surfaces late.