Laravel Addition

[jasperf]

This pull request introduces Laravel support to the Stedding project, allowing it to handle both Laravel and WordPress sites with shared provisioning and deployment workflows. Key changes include the addition of Laravel-specific roles, configurations, and environment settings, as well as updates to existing files to support conditional provisioning based on the site_type property.

Laravel Support Integration:

• Documentation Update: Added a comprehensive guide to LARAVEL.md detailing how Laravel support works, including the use of site_type: laravel in wordpress_sites.yml, Laravel-specific roles, and deployment instructions.
• New Roles and Tasks: Introduced laravel-setup and laravel-install roles with tasks for creating directories, managing .env files, running Artisan commands, and configuring Laravel-specific settings. [1] [2] [3] [4]

Configuration Updates:

• Environment Variables: Updated group_vars files to include Laravel-specific environment variables for development, staging, and production, such as database credentials and application keys. [1] [2] [3]
• Site Definitions: Added Laravel site configurations to wordpress_sites.yml for all environments, specifying site_type: laravel and other necessary properties. [1] [2] [3]

Deployment Enhancements:

• Conditional Provisioning: Updated deploy.yml and dev.yml to conditionally run roles based on the project_type property, ensuring tasks are executed only for the appropriate site type. [1] [2]
• Project Type Detection: Added logic to initialize.yml to determine the project type (Laravel or WordPress) dynamically during deployment.

Miscellaneous:

• Default Settings: Introduced Laravel-specific default environment settings in roles/deploy/vars/main.yml, ensuring compatibility with the existing WordPress workflow.

[jasperf]

Key generation task missing still. And Trellis CLI could also use a tag site_type to install laravel using laravel new site as option besides Bedrock.