wardenenv/warden

[env] A "local" project will never include PHP

bap14 opened this issue · 1 comments

bap14 commented

Version of Warden

0.14.1

Operating System and Installation Method

MacOS Ventura 13.4.1 via Brew

Describe the Bug

When initializing a new project with the "local" variant, there is no way to bring the environment up with a PHP instance. You can still enable different services that rely upon the PHP service (e.g. Blackfire) but the startup will fail because of the missing php-fpm service.

My proposal is to remove the restriction on "local" and instead convert it to an enabled service like any other service (MariaDB, ElasticSearch, etc.).

To Reproduce

  1. Create a new project
  2. Initialize a local project: warden env-init test local
  3. Set the PHP_VERSION=8.2 configuration
  4. (Optional) Enable Blackfire support
  5. Start the environment: warden env up

Expected Behavior

The selected PHP version service is running.

Additional context

No response

bap14 commented

Nevermind, this is because the local one specifically has nothing in there. What would be good is to have a command to help build / identify the Warden image names to use. Example warden image php-fpm would provide the URL to use for the php-fpm images inside your .warden/warden.env.yml file.

  • 👀1