Create post-install script to automatically generate security key and add it to .env.example if necessary (i.e. initial project setup)

[vidurb]

I think the title suffices for explanation. It'd be simple enough to implement and would ensure that the first time any project is created a corresponding security key is added to the repo so that the next person to clone does not need to set it up.

[rungta]

Good idea. However, Craft already does this for us as part of its setup script. I think it is this one https://github.com/miranj/craft/blob/master/composer.json#L45 So our script will simply need to copy the value from the freshly created `.env` and update that in `.env.example` as well.

…

On 30-Apr-2019, at 11:21 AM, Vidur Butalia ***@***.***> wrote: I think the title suffices for explanation. It'd be simple enough to implement and would ensure that the first time any project is created a corresponding security key is added to the repo so that the next person to clone does not need to set it up. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.