Add installation command, fix config overwrites

[toitzi]

Fix group names for pulishing config and assets.

Closes #6645

Q	A
Branch?	4.0
Tickets	Closes #6645
License	MIT
Doc PR	api-platform/docs#1989

[toitzi]

Note: Some first-party packages, such as Laravel Telescope or Laravel Horizon, provide an artisan command like php artisan horizon:install to publish service provider stubs, configs, and assets. If you're interested, I can include a similar command in this PR and update the documentation accordingly to reflect this feature.

Let me know if this is something you'd like to incorporate!

[soyuka]

If I understand correctly the configuration won't be copied on package install right? Indeed I think we should introduce such a command and add it in the composer.json scripts so that's there no other step then composer require api-platform/laravel

[toitzi]

Yes, while the config won't be copied by default, however this is actually expected behavior for Laravel packages. Even first-party packages like Telescope, Horizon, etc., do not automatically publish configs and assets upon installation. You can see this reflected in their installation instructions (Telescope, Horizon, Scout). The Laravel documentation on package development also outlines this as standard practice in the Laravel ecosystem.

While I'm not deeply familiar with composer post-install/update scripts, they seem to run every time commands like composer install or composer update are executed, which would risk overwriting configs repeatedly. However, if you prefer handling it that way, I can certainly give it a try.

[soyuka]

I was thinking that if we create our own api-platform:install command, we could definitely just check if the file exist and not replace it if it does?

Also, I see by using composer create-project laravel/laravel that some commands are executed by default:

see also https://github.com/laravel/laravel/blob/11.x/composer.json#L32-L47

I really think that we should have the less steps possible to start a new api platform project, and I agree that replacing the configuration file is not good. @dunglas any opinion on this?

[dunglas]

I'll go for the api-platform:install command. Let's use Laravel conventions as much as possible.

[toitzi]

I added the install command, also updated the documentation PR.

[dunglas]

LGTM

[dunglas]

Thanks!!