boost:udpate overrides mcp config

[dansan92]

Laravel Package Version

1.6.0

Laravel Version

12.36.0

PHP Version

8.4.5

System Info

Windows 10, WSL2 on Ubuntu with Docker

Description

I'm running a Docker compose dev setup where Laravel is installed in a subdirectory laravel of my project root.

.vscode
.github
.docker
laravel/* <-- laravel installed in here
...

In my container the workdir is set to the laravel folder, so I can see why it assumes this is the root. I don't use dev containers, just a simple bind mount for simplicity.

When I run php artisan boost:install the generated files appear within this laravel folder, which isn't correct. For my setup it places a new .vscode/mcp.json and .github/copilot-instructions.md inside this folder, so I need to manually transfer those to the WSL project root which is one folder above.

php artisan boost:update also overwrites the changes I perform for mcp.json, which I manually set to:

"command": "docker",
"args": [
  "compose",
  "exec",
  "-T",
  "php",
  "php",
  "artisan",
  "boost:mcp"
]

It insists on reverting it back to:

"command": "php",
"args": [
    "artisan",
    "boost:mcp"
]

This command wouldn't work on my WSL for two reasons: no php and artisan not present in current folder.

I think this could be solved by allowing us to specify the project root or installation directory somehow, in my case one folder above laravel. And I don't see why it should overwrite mcp.json after running update, would there ever be something to update there?

I'm also curious, should AGENTS.md (I'm using Codex) and boost.json be within my laravel folder, or my WSL project root? I assume they need to be in the same folder as artisan?

Steps To Reproduce

php artisan boost:install or php artisan boost:update

[pushpak1300]

I’m not entirely sure we needs a separate directory solution at this point, but your MCP config update issue makes sense. I’ve opened a merge request for that #334

Thanks.