Message:

This question already has answers here:

My Answer:
There is no definitive answer to this question as it ultimately depends on the specific requirements and security considerations of your application.

Using a non-public config.ini.php file can provide a more secure way to store sensitive information such as database connection details, as it is not accessible to the public. However, it is important to ensure that the file is properly secured and not accessible through web requests.

On the other hand, using environment variables in the Apache2 server can also be a secure option, as they are not directly exposed in the code and can be managed at the server level. This approach can also make it easier to manage different configurations for different environments (e.g. development, staging, production).

Ultimately, it is recommended to consider the specific security requirements of your application and choose the method that best fits your needs. It is also important to follow best practices for securing sensitive information, such as using encryption and access controls.

Rate this post

4 of 5 based on 7988 votes

John Davidson

apache - DB connection in a non-public config.ini.php or as environment variable in apache2 server?