New app:setup Options in Witty Workflow for Faster Setup

For those using Witty Workflow to streamline Laravel project setups, they’ve recently added new options to the app:setup command that make initializing projects even faster and more flexible. I thought this could spark some interesting discussion for anyone looking to optimize the app setup!

The new app:setup options are:

--no-key: Skips generating the application key (ideal if APP_KEY is already configured).

--production: Runs npm run build instead of npm run dev for production-ready assets.

--minimal-seed: Seeds only essential data, skipping demo content for leaner databases.

--no-composer: Bypasses Composer dependency installation (great for pre-installed environments).

--no-npm: Skips NPM dependency installation (perfect for backend-only setups).

These options seem designed to give developers more control, whether you’re prototyping locally, setting up CI/CD pipelines, or deploying to production. For example, combining --minimal-seed and --no-npm could save time for backend-focused projects.

For those using Witty Workflow, how are you finding these new options? Are they fitting into your setup process, or are there other automation tools you prefer for Laravel? If you haven’t tried Witty Workflow yet, do these kinds of setup optimizations sound useful for your projects? Curious to hear your thoughts or other workflow tips!