This PR changes two things in the installation instructions of the README.md.
First, publishing the package config only works once the service provider is registered. Otherwise the service provider class is not found and nothing gets published. That's why I switched the steps around.
Second, running php artisan vendor:publish --provider="SimonSchaufi\LaravelDKIM\DKIMMailServiceProvider" will publish all assets of that service provider. Since this package's DKIMMailServiceProvider extends Illuminate\Mail\MailServiceProvider, the assets of the base class will also be published. This includes default views and resources which are usually not needed when installing this package. I am pretty sure that this is what happened here: https://github.com/simonschaufi/laravel-dkim/discussions/5
Therefore I added --tag dkim-config to the command as a filter, so only the config/dkim.php will be published.
Thank you for creating this package! :pray:
This PR changes two things in the installation instructions of the
README.md
.First, publishing the package config only works once the service provider is registered. Otherwise the service provider class is not found and nothing gets published. That's why I switched the steps around.
Second, running
php artisan vendor:publish --provider="SimonSchaufi\LaravelDKIM\DKIMMailServiceProvider"
will publish all assets of that service provider. Since this package'sDKIMMailServiceProvider
extendsIlluminate\Mail\MailServiceProvider
, the assets of the base class will also be published. This includes default views and resources which are usually not needed when installing this package. I am pretty sure that this is what happened here: https://github.com/simonschaufi/laravel-dkim/discussions/5 Therefore I added--tag dkim-config
to the command as a filter, so only theconfig/dkim.php
will be published.