Recipes - One-Click Development Actions
Streamline your workflow with one-click actions for common or laborious chores. Recipes automate repetitive development tasks, freeing you from tedious manual work.
Using Recipes
Running a Recipe
Navigate to the Recipes tab, find the recipe you want, and click the card to open details. Review what the recipe will do, then click Proceed to start execution. You'll see live output as the recipe runs, with each step clearly marked by its status.
Upon completion, you'll get recommended next steps and relevant resources.
Example Recipes
DevWorkspace Pro includes recipes for common development workflows. This list shows examples of current recipes—the full collection is constantly expanding based on user needs and feedback.
Laravel Version Upgrades
Automatically upgrade your Laravel project using Rector. The recipe detects your current version, calculates the next upgrade step, and runs Rector with the appropriate rules. Progress and output stream in real-time.
Dependency Installation
Install development tools like driftingly/rector-laravel with one click. The recipe handles Composer integration and shows real-time feedback as packages are installed.
Code Formatting
Configure and run formatters like Laravel Pint. The recipe auto-generates configuration files and handles execution with real-time output.
Code Analysis & Transformation
Use Rector to transform and modernize your code automatically. The recipe generates necessary configurations and streams output as it processes your codebase.
And More...
The recipe library continues to grow with automation for database setup, git workflows, package management, environment configuration, and other common development tasks.
If you'd like to request a new recipe for a workflow you frequently use, open an issue on GitHub with details about what you'd like to automate. Community feedback drives recipe development.
Best Practices
Before running a recipe, ensure you have a clean git index by committing your current changes to git:
git add .
git commit -m "..."After completion, review the changes made by the recipe:
git diffRun your test suite to ensure everything works as expected, then commit the recipe's changes to git:
Troubleshooting
If a recipe shows as unavailable, read its status message—it explains precisely what's needed. Common issues include missing dependencies (install them first), project not running (start your DDEV project), or already completed (no action needed).
If a recipe fails during execution, review the error output to understand the issue. Fix the problem and run the recipe again.