Suggest publishing the config after installing

[jackmcdade]

No description provided.

[jasonvarga]

I don't think many packages really suggest doing that.
The docs already mention to do it, and give you a copy/pasteable command.

Not enough?

[jackmcdade]

I've definitely seen it before, and given that the defaults probably won't work for anyone's site right out of the box, it seems like a good idea to me. I can remember to type composer require statamic/ssg without the docs, but I can't remember the syntax for vendor publish without pulling up the docs.

[jasonvarga]

Okay. 👍

PS. You can just run artisan vendor:publish which is easy to remember, and you can just pick from the list so you don't have to remember the specific arguments.

[jackmcdade]

TIL <3

…

On Jan 10, 2022, at 3:52 PM, Jason Varga ***@***.***> wrote: Okay. 👍 PS. You can just run artisan vendor:publish which is easy to remember, and you can just pick from the list so you don't have to remember the specific arguments. — Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https:/notifications/unsubscribe-auth/AAAK5Q3NVLKDJI2QGFNQYH3UVNBJZANCNFSM5LUS467A>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[duncanmcclean]

With Statamic 5 and the introduction of the php please install:ssg command, developers will be given the choice of publishing the config file. See statamic/cms#9622.