- How do I install tightenco/quicksand in a Laravel application?
- Install it as a development dependency with composer require tightenco/quicksand --dev, then publish its configuration file using the standard vendor:publish Artisan command. Keeping it out of production dependencies matches its purpose as a local and testing tool. Check the repository's composer.json first, because the package is archived and its Laravel version constraints have not been widened since Laravel 11.
- Does Quicksand support Laravel 11 or Laravel 12?
- The newest documented compatibility target is Laravel 11, and the last tagged release was 2024-03-12. The repository is archived, so no Laravel 12 support release is expected. Read the actual constraints in composer.json rather than inferring from release notes, and plan an exit path or a small internal fork if you upgrade past Laravel 11.
- How does Quicksand stop me from wiping a production database by accident?
- Quicksand is built around environment protection and confirmation safeguards so a destructive reset cannot be triggered casually against a production connection. It also encourages pointing the work at a dedicated sandbox connection rather than your application's primary one. You should still review the guard logic in src/ before handing it credentials that can drop tables.
- Can Quicksand run migrations and seeders after resetting the database?
- Yes, the documented workflow supports running migrations after a reset, with seeding available as a follow-up step. The sandbox approach runs your migrations against a throwaway database first, so failures and destructive schema changes surface before they reach a real database. Once the dry run succeeds, you apply the changes for real.
- How do I configure the sandbox database connection for Quicksand?
- Quicksand publishes a configuration file where you define which connection it should use for sandbox runs. Add a separate entry in config/database.php pointing at a disposable database, then reference that connection name in the Quicksand config. Keep those credentials scoped to non-production hosts only.
- Can I run Quicksand in a CI pipeline or automated test suite?
- It is a development-time tool, so it fits naturally into local workflows and CI jobs where you can provision a disposable database. In CI the sandbox connection needs its own credentials with schema-mutating privileges, which is typically the step that stalls adoption. Treat pipeline failures as useful signals about risky migrations, but budget time for the credential approval conversation with platform or security.
- What are the alternatives to Quicksand for safe Laravel database resets?
- For schema resets, Laravel's built-in migrate:fresh and migrate:refresh commands plus the RefreshDatabase trait in tests cover most needs without a third-party dependency. For validating migration SQL, running migrations against a scratch database or a containerised MySQL or Postgres instance in CI achieves a similar gate. If your actual problem is deleting aged soft-deleted rows, Laravel's native Prunable trait and model:prune command are the first-party answer.
- Is tightenco/quicksand still maintained?
- No, the repository is archived; the last release was 2024-03-12 and the newest documented change is Laravel 11 compatibility. There are no recorded dependents, so you would be the first party to discover breakage on a newer Laravel major. Adopting an archived package is effectively forking it, so plan for owning the code if you commit to it.
- Is Quicksand a soft-delete pruning package or a migration sandbox?
- Quicksand is documented as a development-time database reset and migration sandbox tool, not a data-retention pruner. Some package metadata has circulated describing scheduled cleanup of soft-deleted Eloquent records, which is a different problem that Laravel's Prunable trait already solves natively. Read src/ and composer.json before adopting so you know which behaviour you are actually installing.
- What database permissions does Quicksand need for its sandbox connection?
- The sandbox connection needs privileges to create, migrate, and drop schema objects on a non-production database. Production credentials that deny CREATE and DROP will block the tool entirely, so request a dedicated non-production credential set approved by your security team. If your organisation requires an audit trail for destructive operations, that is a separate logging concern Quicksand does not provide.