## Bug Report: `php-fpm` Error and Incorrect `reward info` Status for Node.js Environment
### Description
When running `reward env up` for a Node.js + MySQL environment (non-PHP), I encounter the error: `service "php-fpm" has neither an image nor a build context specified: invalid compose project`. Running `docker compose -f .reward/reward-env.yml up -d` successfully starts the containers (`node` and `db`), but `reward info` incorrectly shows "Environment Status: Stopped" despite the containers running. This suggests issues with Reward’s handling of the `local` environment type and its state tracking.
### Steps to Reproduce
1. Initialize a new Reward environment in the project directory (`~/Sites/my-node-react`):
```bash
reward env-init node-react
.envfile (my-node-react-project/.env):.reward/reward-env.ymlfile:~/.reward/.envto override PHP defaults:reward env up:service "php-fpm" has neither an image nor a build context specified: invalid compose project.docker compose -f .reward/reward-env.yml up -d:nodeanddb) start successfully, verifiable withdocker ps.reward info:Expected Behavior
reward env upshould start the environment without including aphp-fpmservice, respectingREWARD_PHP_ENABLED=falseand the project’s.reward/reward-env.ymlwhich defines onlynodeanddbservices.reward infoshould show "Environment Status: Running" when containers are active, whether started viareward env upordocker compose.Actual Behavior
reward env upfails with the error:service "php-fpm" has neither an image nor a build context specified: invalid compose project.reward infoincorrectly reports "Environment Status: Stopped" after starting containers withdocker compose -f .reward/reward-env.yml up -d.Environment
Additional Information
php-fpmservice appears to be included by Reward’s defaultlocaltemplate, despite settingREWARD_PHP_ENABLED=falsein both project and global configurations.docker compose -f .reward/reward-env.yml up -dbypasses thephp-fpmerror, confirming the project-specific configuration is correct.rm -rf ~/.reward/cache) and reinitializing the environment (reward env-init node-react) did not resolve the issue.reward infocommand fails to detect running containers, suggesting a bug in Reward’s state tracking for non-PHP environments or when usingdocker composedirectly.--forceflag inreward env-init node-react --forcewas unsupported, as noted previously, requiring manual.envdeletion to reinitialize.Suggested Fix
REWARD_PHP_ENABLED=falseand excludesphp-fpmfrom thelocalenvironment template for non-PHP projects.reward infoto accurately reflect container states when containers are started viadocker composeor when bypassing Reward’s internal templates.localenvironment type.Workaround
docker compose -f .reward/reward-env.yml up -dto start the environment without errors.docker compose -f .reward/reward-env.yml down.docker-compose.ymlto avoid Reward entirely: