You just need to define unique environment variable for each peace of data that needs to be changeable between different environments.įor example: DB_HOST, DB_USER, DB_PASSWORD. This is normally done by means of environment variables. The better approach would be to externalize this data and pass it to your application during execution.
It's very easy to leak this sensitive data. This is a serious security violation, because production-grade configuration data and passwords shouldn't be stored in code. You will have to release a new version of the application to change those values. Hardcoding those values make it difficult to change them later on. Actually, I would not recommend to store configuration values like database connection information, passwords, access tokens and such inside of actual application code for the following reasons:
0 kommentar(er)
