Weave Code
Acacia Laravel Package
savannabits/acacia
Acacia by Savannabits is a Laravel admin panel and CRUD toolkit that scaffolds controllers, models, and Inertia/Vue screens, with built-in authentication, roles, and permissions—helping teams ship polished management interfaces quickly without rewriting the same boilerplate.
Acacia is a Laravel package for quickly building admin panels and CRUD interfaces for Eloquent models. It reduces boilerplate with reusable admin scaffolding, sensible defaults, and Laravel-native routes, controllers, and views.
- Generate CRUD screens for Eloquent models
- Reusable admin layouts and UI components
- Configurable navigation and menus
- Laravel-native, extensible controllers and views
- Easy customization for fields, actions, and workflows
Frequently asked questions about Acacia
- Does savannabits/acacia support Laravel 10 and Laravel 11?
- Acacia's last release is v1.4.0 from May 2022 and its composer constraints target the Laravel 9.2 era with PHP 8.0 and 8.1. Installing on Laravel 10, 11, or PHP 8.3 should be treated as unsupported until you verify it in a spike branch. Diff the package's own composer.json constraints against your composer.lock rather than trusting the README, and budget a fork-and-patch task for every Laravel major upgrade.
- How do I install savannabits/acacia in a Laravel application?
- Install it with composer require savannabits/acacia, then publish the package's config, stubs, views, and migrations before running the generator command. Because the package is dormant, run the install inside a spike branch first so you can see exactly how it boots and what it emits. Commit the published stubs and generated resources to your repository, since those files become first-party code under your change control.
- Does Acacia generate Blade views or Inertia with Vue 3?
- The package description advertises Vue 3 and Tailwind 3 through the jetstream-inertia-generator lineage, while other documentation describes Blade-rendered views. Inertia and Blade are very different integration jobs with different Vite, alias, and Tailwind content-glob work, so do not estimate until a spike branch shows what the generator actually emits. Inspect the published stubs and views to confirm which front-end stack ships.
- Is savannabits/acacia still maintained?
- No, Acacia is effectively dormant. The latest release is v1.4.0 from 2022-05-11, with roughly 43 GitHub stars, zero dependents, and one effective maintainer. Treat it as a scaffold to fork or vendor rather than a platform bet, and name an owner for the fork before adoption.
- Does Acacia work with spatie/laravel-permission?
- Acacia fits a Laravel monolith that already has spatie/laravel-permission installed for an internal back-office surface such as users, roles, and moderation queues. Verify the package's pinned permission-package constraint against your composer.lock before installing. Generated search and sort code that relies on LIKE '%term%' queries can also need indexing work once tables grow beyond seed data.
- What happens if I re-run the Acacia generator over files I've already edited?
- Assume the generator clobbers the files it manages. Re-running it on a dirty tree can destroy hand edits, so commit or stash before every run and review the diff afterwards. The safest workflow is to generate once into a clean branch and then treat the output as hand-maintained code.
- Does Acacia create a default admin user when seeding?
- Yes, v1.4.0's only change was adding a default admin user to the Users Seeder. If that account is hardcoded and ungated it is a predictable privileged account and a likely penetration-test finding. Before shipping, make it environment-variable sourced, hashed, created with firstOrCreate, and gated so it only runs in the intended environments.
- Can I remove savannabits/acacia after generating my CRUD screens?
- Yes, and it should survive removal. Config, stubs, views, migrations, and generated resources are all committed in your repository, so only the generator command and service provider come from vendor. Document the exit path and confirm the generated output still works with the composer dependency deleted.
- Is Acacia a good fit for multi-tenant apps or API-first backends?
- No. Acacia does not fit an API-first backend, a customer-facing UI that must match a design system, or multi-tenant isolation that isn't expressible in its publishable stubs. It targets internal back-office CRUD screens and admin panels rather than differentiated product surfaces.
- What are alternatives to Acacia for scaffolding Laravel admin panels?
- Common alternatives include nwidart/laravel-modules for modular structure, the jetstream-inertia-generator lineage Acacia is inspired by, and full admin frameworks such as Laravel Nova or Filament. Acacia's value is the generated first-party code you own, so compare it against the roughly two to four hours a competent Laravel developer spends hand-building the same CRUD screen. Given its low adoption signal, treat it as a cheap trial rather than a commitment.
Weaver
How can I help you explore Laravel packages today?