Now that .env is available, can we have a common app.php?

behavior

#1

Hello everyone!

This is a more of a ‘best practices’ question.

Since 3.5, we have the option to use a .env file in order to define configuration options like timezone, locale and database credentials.

So I’m wondering, should I commit app.php and use it across all environments, and keep everything in .env?

Or is it still important to have it stay out of version control? If so, why?

Thanks for the input!


#2

You shoud not commit security salt, email, database passwords. These are the sensitive parts of app.php.


#3

Thanks for the reply!

All of this has been moved to my .env instead :slight_smile:
So I guess it’s fine to commit app.php then