Could the Laravel application key be in the remote repository?

Question

I have developed a Laravel app locally and push the app to my server via GitHub Action. On the server, I still have to adapt the .env.template, as the .env does not belong in the repository.

Question: Do I have to regenerate the Laravel app key in production or staging or use the one from local? If not, I would also copy the key into the .env.template or .env exampel.

You should regenerate your app key for every different environment — Jan-Willem de Boer, Dec 05 '22 at 13:54
[Tighten.com : APP_KEY And You](https://tighten.com/blog/app-key-and-you/) — steven7mwesigwa, Dec 05 '22 at 14:16

score 1 · Accepted Answer · answered Dec 05 '22 at 13:58

1

It is generally recommended to use a different application key in each environment (i.e., production, staging, and local) in Laravel.

This is because the application key is used to encrypt and decrypt sensitive data in your Laravel application, and using a different key in each environment can help prevent security issues and ensure that your data remains secure.

answered Dec 05 '22 at 13:58

May

51
3

1

Thank you for your answer! This also confirms my feeling to generate a new key. – Maik Lowrey Dec 05 '22 at 14:19

Could the Laravel application key be in the remote repository?

1 Answers1